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
>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.
[quoted text clipped - 15 lines]
> Thanks
> Charles
Charles - 28 Mar 2006 18:46 GMT
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
> 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
[quoted text clipped - 23 lines]
> > Thanks
> > Charles