DNS at remote sites

[Justin]

We have a domain controller at our corporate office that
uses DNS (Active directory integrated zone). We later
added domain controllers at each of our remote locations.
Should the NIC settings on the remote location servers
point to themselves for DNS or should they point to the
corporate office? Where should we point the clients to?
Here are some of the problems we've had with the various
scenarios:
1. When the server is pointed to itself for dns, we can
only see the local subnet instead of the whole domain.
2. We can't turn on forwarders on the DNS zone at the
remote locations, so internet browsing doesn't work if
the clients are pointed to the remote location server.
3. If the clients or servers are pointed to the corporate
office for DNS, any problems with the WAN results in the
remote locations losing their DNS service.

Can someone tell me the correct way to set this up?

 

[Michael Johnston [MSFT]]

1. The DCs should point to themselves for primary DNS and a DC in the main site for secondary DNS.
2. If any of the DNS servers have a "." root zone, delete this zone. Close the DNS MMC and reopen it. Now you should be able to add forwarders.

That should solve any of the DNS problems you are experiencing.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.