I'm dealing with some frustrating DNS issues on my local network, and I'm hoping someone can help. I've got a domain controller running on a Hyper-V VM, and it's also set as the DNS server. The network is isolated with no internet connection, and all devices connect directly to switches along with the DC's physical host. Lately, we've been getting this error message whenever someone tries to use Remote Desktop or applications that require Windows Authentication: 'The system cannot contact a domain controller to service the authentication request. Please try again later.'
When I run nslookup, it says 'DNS request timed out'. I recently fixed the server's incorrect time, and it worked temporarily, but the issue has come back. To make things work again, I often have to run the following commands on each client:
- ipconfig /flushdns
- ipconfig /registerdns
- Disable and re-enable the network card
If those don't work, restarting the client usually helps, but the DNS issue returns within a few hours. Notably, many client machines aren't showing the domain name under network settings; instead, they just say 'network 5'. I'm pretty sure this is a DNS issue but can't pinpoint the root cause. Any suggestions?
2 Answers
Can you post a sanitized 'ipconfig /all' output from one of the affected PCs? That might give us more insight into the issue.
Is this your only domain controller? If so, it’s crucial to have good DNS settings both on the DC and on the client PCs to ensure proper communication. Also, regarding the time issues, have you checked that the time sync service is disabled? You may want to ensure one DC (often the PDC emulator) is configured to sync with a reliable external time source. This could help stabilize time across your network.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures