Yep, to illustrate this point, run nslookup xyz.com. You'll get a return of all the IP addresses (hopefully) of your DNS servers. If you start adding empty A record names pointing to your web servers, they'll get listed in the return. This is problematic if your clients are looking for DNS servers of xyz.com zone and get returned a web server IP address as the first in the list.
-m -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phil Renouf Sent: Friday, April 29, 2005 12:27 PM To: ActiveDir@mail.activedir.org Subject: Re: [ActiveDir] ACTIVE DIRECTORY AND WEBSITE CONFLICTS On 4/29/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > He is. That is why they are able to resolve xyz.com externally. > Yes, but if accessing www.xyz.com is all he is after and there is not a www alias on his AD DNS already then he should be able to add www and point it to the IP of the website. If he wants the users to be able to browse to xyz.com without the www then as Deji said he's pretty much out of luck. Phil List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
