when relevant content is
added and updated.
I got this error today when trying to log into the only DC at one of our client sites. Needless to say this is a bad sign when a DC can’t see it’s own domain. After a few checks I quickly found that none of the machines could log into the domain at all. Didn’t take me long to figure out that DNS must be hooped. To get it working I logged in locally on another server, opened up services.msc, connected to the DC by IP address and stopped and started the DNS server service, and just like that everything came back. Now here is the rant, DNS is so tightly integrated with AD that you can get these catch-22 scenario’s where you can’t log into a server because DNS isn’t working but you need to log in to fix DNS. While one can easily restart a service from another machine, any other in depth troubleshooting is difficult especially since in this situation it would have been a 45 minute drive to get to the physical box.