I'm dealing with some frustrating DNS problems related to my domain controller that's running on a Hyper-V virtual machine. This DC also functions as the DNS server for a small local network that, notably, doesn't have internet access. All devices are connected directly to its physical host server via switches. Lately, we've been getting an error message when attempting remote desktop connections or using 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, I get a "DNS request timed out" message. Last week, I noticed the server's time was incorrect, and after fixing it, it worked fine for a few days, but the issue resurfaced. Currently, the workaround to get the computers functioning again involves running these commands on each device: ipconfig /flushdns, ipconfig /registerdns, disabling and enabling the network card, or just restarting the computer. However, the problem reappears a few hours later. Additionally, I noticed that almost all computers show 'network 5' instead of the actual domain name under the network card settings. I'm almost certain this is a DNS issue, but I'm having trouble pinpointing what's wrong.
2 Answers
Is your domain controller the only one in the network? It's important to know so that we can troubleshoot effectively.
Could you share the output of the 'ipconfig /all' command from one of the affected PCs? That could help identify if there's a misconfiguration.
Yes, it is the only DC.