Has anyone run into problems with DNS failing on a Domain Controller? We keep experiencing this issue where the DNS service fails. Initially, we suspected it might be a port conflict with QuickBooks, but after addressing that, the problem persists. We've tried restarting services, removing and rebuilding the DNS server, but the only 'temporary' fix seems to be a reboot. However, the problem pops up again the next day. Could it be related to TTL settings? It almost feels like the settings don't stick after a reboot. We've also run nltest /sc_verify and reset the secure channel, and we've ensured that our DNS and DC only point to valid internal servers. We restarted the Netlogon and DNS services for SRV record registration and ran dcdiag /test:dns and repadmin /replsummary to check the replication and DNS zone health. Other workstations are fine, except for one specific workstation and this Domain Controller. Just a note – this server serves as both a file server and a Domain Controller, and it's running Windows Server 2019.
2 Answers
Sounds like you need to dig deeper into the server setup. Can you share more about the OS version and any recent changes? Maybe a DNS error popped up in your logs. Sometimes rebooting helps, but if DNS won’t resolve the file server, that’s definitely an issue. You could also try pinging the server directly and see if that provides any hints.
Why is QuickBooks running on a domain controller? It seems like this server is doing way too much. If it's a small company setup, they might not have the budget for separate servers, though it’s not ideal to mix roles like that.
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