You WILL have problems. You have 1 good solution and 1 very bad and stupid (non-)solution. 1. Good. Educate your users that, because of the way you've designed AD and your Domain names, they will ALWAYS have to append www. to get to your website. 2. BAD. Ridiculous. Stupid. Asinine. Fill-in-more-expletives. Install IIS on your DCs and put up a web page that redirects to your REAL web server. Then any http request that hits the DCs, using the domain name (with www) will be auto-forwarded to your web server. I'd break your legs IF you install IIS on MY DC. This is one of the strongest arguments for naming your external and internal domains separately. Sincerely,
D�j� Ak�m�l�f�, MCSE MCSA MCP+I Microsoft MVP - Directory Services www.readymaids.com - we know IT www.akomolafe.com Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon ________________________________ From: [EMAIL PROTECTED] on behalf of Doug M. Long Sent: Mon 8/9/2004 10:07 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Kinda OT: DNS entry That is pretty much how we have it set right now...BIND for public facing DNS, which causes no problems. But, the internal DNS servers still need to point domain.edu to the web server, as those are the DNS servers that everyone on campus actually points to. How do I get around them possibly resolving the wrong IP when going to domain.edu in a browser? As it stands now, there is a possibility they will resolve to the IP of a DC. ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond Sent: Monday, August 09, 2004 12:18 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Kinda OT: DNS entry Hi Doug, The situation you're describing is called split DNS, and is rather common. What you have in this scenario is two sets of DNS servers - internal (AD), and external (public facing). Your public facing DNS servers have things like the Internet Ip of your WWW and your MX records and good stuff like that. There's no sign of the AD DNS in your public facing DNS. Internally, you duplicate all the necessary records on the AD DNS as they are in teh external zone, except you may wish to use the private IPs instead if you want. Does this help? --Brian -----Original Message----- From: Doug M. Long [mailto:[EMAIL PROTECTED] Sent: Mon 8/9/2004 9:45 AM To: [EMAIL PROTECTED] Cc: Subject: [ActiveDir] Kinda OT: DNS entry What is the proper way to DNS my domain so that people are pointed to the web server? Currently I have www.domain.edu DNSed to the web server (where domain.edu is our Active Directory domain). I would also like to DNS domain.edu to the web server. Will I run into issues with this? When I DNSed domain.edu to our pop3 server (don't ask why) we were having problems with the mail clients not using the correct DNS entry (because domain.edu was DNSed to two DCs and a front-end pop3 server). Oh yeah, I am using AD integrated DNS (if that matters). Any help is appreciated. List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
