We are currently suffering a problem starting Active Directory following a power down of the domain... When we power up the first domain controller (PDCe) we get the usual delay before logging on, once logged on there are a number of event log errors and Active Directory and DNS will not start. This is a Server 2003 R2 Domain Controller with a Forest and Domain functional level of Server 2003.
When opening AD Users and Computers and try to connect to the domain I receive the following error: "The specified domain either does not exist or cannot be contacted"
When opening the DNS console I receive the following error: "Cannot contact the DNS server". The DC in question is using 127.0.0.1 (as per the MS best practice) as its primary DNS and the IP of a different domain controller as the secondary DNS which wouldn't be powered on at this stage.
I can see a number of issues in the event logs for the DC, including:
1. Replication errors which I would expect given the other Domain Controllers aren't powered on at this stage
2. Event ID 1126: Active Directory was unable to establish a connection with the global catalogue
1. Event ID 4013: The DNS server was unable to open the Active Directory. This DNS server is configured to use directory service information and can not operate without access to the directory. The DNS server will wait for the directory to start. If the DNS server started but the appropriate event has not been logged, then the DNS server is still waiting for the directory to start.
It appears that DNS will not start without Active Directory and Active Directory will not start without DNS!
We've looked at this for a couple of days with one of our Microsoft Gold Partners with no success. Any ideas or guidance would be greatly appreciated.