I am a consultant with a client who has DNS setup a zone setup
internally with the same name as the public DNS, thecomapanyname.com.
The DNS server is on a Windows 2003 server Integrated with AD. This
server also has a public Web site on it. All workstations are set with
a primary DNS for the Windows 2003. The DNS server is setup with
forwards to the ISP Nameservers. I just promoted a second server and
setup a second AD integrated DNS server which appears to have
replicated DNS as is should. Besides the obvious that DNS originally
was not setup correctly which I had nothing to do; I have two
questions:
1. Normally the users resolve thecompanyname.com with the local IP and
can bring up the Web site. What would cause the users to suddenly
start resolving to the public IP?
2. Is there any documentation someone can point me to which states DNS
zones should not be the same private and pubic names? I would like
something from Microsoft to show my client.

Thanks
Charles

Do an nslookup and see what server is performing the name resolution. In a
Windows domain, ONLY local AD DNS servers are allowed. You can list your on
DCs as preferred and aternates, but you should not list your own as
preferred and a public as alternate. My first guess is that the clients are
resolving the public name from the public DNS server.

....kurt

"Charles" <cbanks@bjtsupport.com> wrote in message
news:1143467920.033755.185250@i39g2000cwa.googlegr oups.com...
>I am a consultant with a client who has DNS setup a zone setup
> internally with the same name as the public DNS, thecomapanyname.com.
> The DNS server is on a Windows 2003 server Integrated with AD. This
> server also has a public Web site on it. All workstations are set with
> a primary DNS for the Windows 2003. The DNS server is setup with
> forwards to the ISP Nameservers. I just promoted a second server and
> setup a second AD integrated DNS server which appears to have
> replicated DNS as is should. Besides the obvious that DNS originally
> was not setup correctly which I had nothing to do; I have two
> questions:
> 1. Normally the users resolve thecompanyname.com with the local IP and
> can bring up the Web site. What would cause the users to suddenly
> start resolving to the public IP?
> 2. Is there any documentation someone can point me to which states DNS
> zones should not be the same private and pubic names? I would like
> something from Microsoft to show my client.
>
> Thanks
> Charles
>

Kurt,
Thanks for your response.
I did do an nslookup and it resolved with no errors to the local IP and
(I don't know which domain) local nameserver with domain. DHCP is
setup to only point DNS to the local DNS servers and only the DNS
server has the public as forwards. That is why I don't understand what
happen. I'm sure it has something to do with both local and public
domain name being the same, but I can't find documentation to verify
that.
Charles

Kurt wrote:
> Do an nslookup and see what server is performing the name resolution. In a
> Windows domain, ONLY local AD DNS servers are allowed. You can list your on
> DCs as preferred and aternates, but you should not list your own as
> preferred and a public as alternate. My first guess is that the clients are
> resolving the public name from the public DNS server.
>
> ...kurt
>
> "Charles" <cbanks@bjtsupport.com> wrote in message
> news:1143467920.033755.185250@i39g2000cwa.googlegr oups.com...
> >I am a consultant with a client who has DNS setup a zone setup
> > internally with the same name as the public DNS, thecomapanyname.com.
> > The DNS server is on a Windows 2003 server Integrated with AD. This
> > server also has a public Web site on it. All workstations are set with
> > a primary DNS for the Windows 2003. The DNS server is setup with
> > forwards to the ISP Nameservers. I just promoted a second server and
> > setup a second AD integrated DNS server which appears to have
> > replicated DNS as is should. Besides the obvious that DNS originally
> > was not setup correctly which I had nothing to do; I have two
> > questions:
> > 1. Normally the users resolve thecompanyname.com with the local IP and
> > can bring up the Web site. What would cause the users to suddenly
> > start resolving to the public IP?
> > 2. Is there any documentation someone can point me to which states DNS
> > zones should not be the same private and pubic names? I would like
> > something from Microsoft to show my client.
> >
> > Thanks
> > Charles
> >