Fix Server Not Found Error on Windows Server 2019 DNS

Yeah, that 'Server Not Found' error is a pain. You see it in the browser, in nslookup, and your users are yelling. Let's fix it right now.

The Immediate Fix

Open Command Prompt as Administrator and run these commands in order:

ipconfig /flushdns
ipconfig /registerdns
net stop dnscache && net start dnscache
net stop dns && net start dns

Then check your DNS client service is running:

sc query dnscache

If it's stopped, start it: net start dnscache.

Now try nslookup for a common domain like google.com. If it resolves, you're set. If not, move on.

Why This Worked

The culprit here is almost always a corrupted DNS cache or a stalled DNS Client service. Windows Server 2019 has a habit of holding onto stale entries, especially after a network change or a non-graceful shutdown. Flushing the cache wipes that garbage. Restarting both the client and server services forces a clean state. The registerdns command re-registers your server's own host records with its local DNS zone—often that's what's missing.

I've seen this exact scenario after a DHCP lease renewal. The server gets a new IP, but the DNS cache still points to the old one. Boom, 'Server Not Found' for anything relying on that server's name.

Less Common Variations

Stale DNS Scavenging

If you're running Active Directory-integrated DNS, check your scavenging settings. Run this from an elevated PowerShell:

Get-DnsServerScavenging | Select-Object ScavengingState, ScavengingInterval, RefreshInterval

If scavenging is disabled or the intervals are too long (default is 7 days), stale records pile up. Set it to 1-hour intervals for the refresh and 7 days for scavenging via the GUI or:

Set-DnsServerScavenging -ScavengingEnabled $true -RefreshInterval 1.00:00:00 -ScavengingInterval 7.00:00:00

Forwarder Timeout

Check your DNS forwarders. If they're unreachable, queries fail. Go to DNS Manager, right-click the server, Properties > Forwarders. If you see red X marks next to any IP, remove or replace them with reliable ones (e.g., 8.8.8.8, 1.1.1.1).

Test with: nslookup -type=A google.com 8.8.8.8. If that works but your server doesn't, it's a forwarder issue.

IPv6 Priority

Sometimes Windows Server 2019 prefers IPv6, but your network doesn't support it. Disable IPv6 on the NIC temporarily to test (not a permanent fix, but diagnostic). Go to Network Connections, right-click the NIC, uncheck Internet Protocol Version 6 (TCP/IPv6). If that fixes it, reconfigure IPv6 properly or set prefix policies.

Prevention

Enable automatic scavenging on all AD-integrated zones. Set a reasonable interval—don't leave it at default 7 days if you have dynamic clients.
Monitor DNS logs: Event ID 409 (DNS server) and 1014 (DNS client events). They'll tell you exactly what's failing.
Use static DNS on your servers. Seriously, don't rely on DHCP for DNS server addresses on critical infrastructure. I've seen too many 'Server Not Found' errors caused by a DHCP server handing out a wrong DNS IP.
Schedule a weekly script that flushes cache and restarts services during maintenance windows. Keep it simple:

ipconfig /flushdns
ipconfig /registerdns
net stop dnscache && net start dnscache
net stop dns && net start dns

That's it. This error isn't complicated—it's just lazy caching or a broken service. You've got this.