Mature network, everything was working fine one evening, the next morning no one can access the server because Active Directory has quit communicating with DNS.
We're talking W2K3 servers here... The Server is a domain controller. It has DNS installed on it. You can ping the server name on the network, and it resolves ok.
There are three other DC's at other physical locations. I cannot force replication to another DC, I get the error message that the attempt to connect the Domain Controller failed because the target principal name is incorrect.
Using dcdiag /fix get error that the DC's name couldn't be resolved dcdiag tells me could not confirm the identity of this server in the directory versus the names returned by DNS servers. If there are problems accessing this directory server then you may need to check that this server is correctly registered with DNS
netdiag /test:member /v -- Everything comes back positive, passed, connected --- Domain membership test: Passed
Tried numerous times: restart NetLogon service - ipconfig /flushdns - ipconfig /registerdns - Does nothing
Completely uninstalled and reinstalled DNS on the server, deleting cache.dns, netlogin.dns, netlogin.dnb Cannot not get DNS to create Forward Look UP zones
Anything I try to do with the server, even tried removing it from AD, tells me it can't because it does not see the domain.
Any ideas???
Bookmarks