Server DNS Dependancies
Posted on 2014-02-07
My company recently deployed a domain controller/DFS/DNS server to what will be our second location added to the our domain. We had to reboot our primary domain controller today and it caused our second location to lose DNS services. The error in server manager reads
"The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error."
Obviously having the successful networking operation of our company be contingent upon the status of one machine is not acceptable. The network settings on the non-primary domain controller (we'll call it DC2) point to it's own local IP address for Preferred, and then to 127.0.0.1 for Alternate. It's my understanding that 127.0.0.1 is a 'loopback' IP that would also be pointing to the server. Do these settings imply that DC2's successful DNS resolution is dependent on the primary DC?
Truth be told I'm not a networking guru, I don't understand how our primary domain controller resolves DNS requests as it only points to itself for DNS in network settings, but if you could give me a few sentences that explain the means by which my server pointing to itself for name resolution is somehow finding the IPs it needs and how I can make DC2 not dependent on the primary DC I would greatly appreciate it. We will soon have DC3 and DC4 and I can't have 4 sites go down at the same time.