Joining new DC to AD - DNS name does not exist
- by Andrew Connell
I had a DC fail on me recently and trying to add a new one to my domain, although I'm sensing I might have other issues in my domain. I'm a dev at heart and know just enough about AD to be dangerous so looking for some assistance.
My working DC is RIVERCITY-DC12. I'm trying to promote RIVERCITY-DC14 as a DC to the RIVERCITY domain, but when I run DCPROMO, at the NETWORK CREDENTIALS step where I point to the name of the domain (rivercity.local), I get "An AD DC for the domain rivercity.local cannot be contacted" and in the details see "The error was DNS name does not exist"
Looking at RIVERCITY-DC12, I can see DNS is working, I've been able to query it from other machines in my domain, and no errors are reported in the DNS category within the Event Viewer. When I checked the FMSO roles, it shows RIVERCITY-DC12 is the machine for all listed roles.
Not sure what I should do next or how to troubleshoot/investigate after searching around for a solution... ideas?
Environment:
Domain: rivercity (rivercity.local)
Forest functional level: Windows 2000 (I'm more than happy to raise this)
Windows Server 2008
All servers are Windows Server 2008 R2 SP1 (fully patched)
