DNS Connectivity problems on a Two-AD network
Posted on 2007-07-24
Hi. My client is having DNS connectivity problems on a single subnet network. We recently installed a second DC with AD running. Users all of a sudden have trouble logging onto domain. Have to reboot computer several times. Most PCs are XP. Some Win2000. Once on, they seem to do OK.
The basic configuration is as follows...
DC1 ... Points to its own IP address for DNS. DNS is configured with forwarders to the ISP's dns addresses.
DC2 ... Points to DC1 for DNS and also to itself as alternate DNS.
I had a similar problem with another client sometime back and solved it by making the following configuration changes...
Made a Registry change on the DC that made it ignore Master Browser elections forced by user PCs.
Changed DHCP expiration to two days.
Enabled in DNS, Scavenge Stale Resource Records every 7 days.
Enabled in DNS, allow Nonsecure and Secure dynamic updates.
However on the network having the problem now, I made those changes and they did not fix the problem.
Another note, after the new DC (DC2) was originally configured and brought online, the IT Director at the site shut it down for over a month before finally bringing it back online. She says she saw no error messages and that it seems to be syncing DNS with the first DC (DC1). However I wonder if having it offline for an extended period has caused problems?
What can I do to troubleshoot this?