Fix 'DNS_PROBE_FINISHED_NXDOMAIN' in Chrome on Windows 11

Quick answer: Open Command Prompt as admin and run ipconfig /flushdns, then ipconfig /registerdns. If that fails, change your DNS to 8.8.8.8 and 8.8.4.4.

When Chrome throws DNS_PROBE_FINISHED_NXDOMAIN, it means the domain you typed doesn't resolve to an IP address. That could be a typo, but often it's your DNS server being slow or broken, or your local hosts file blocking the site. This error trips up beginners all the time, and I've seen it on Windows 11 especially after a network switch or a VPN disconnect. Here's how to fix it for good.

Fix 1: Flush the DNS cache

Windows caches DNS lookups to speed things up, but that cache can get stale or corrupted. Clearing it forces your PC to ask the DNS server fresh.

1. Press Win + X and choose Terminal (Admin) or Command Prompt (Admin).
2. Type these commands, pressing Enter after each:

ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew

Wait for each command to finish. The last two renew your IP lease, which often clears network quirks. Restart Chrome and try the site again.

If the error sticks, move to the next fix.

Fix 2: Switch to a public DNS server

Your ISP's DNS might be down or just slow. Google's public DNS is free and reliable. Here's how to set it on Windows 11:

1. Open Settings (Win + I) and go to Network & Internet.
2. Click Wi-Fi or Ethernet depending on your connection.
3. Find your network name and click the Edit button next to DNS settings.
4. Set the dropdown to Manual, turn on IPv4, and enter:

Preferred DNS: 8.8.8.8
Alternate DNS: 8.8.4.4

Save and restart your browser. This is the solution I recommend most because it bypasses flaky ISP DNS entirely.

Fix 3: Check the hosts file

A manual entry in your hosts file can override DNS and cause this exact error. I've seen malware or leftover VPN configs add bogus lines there. To check:

1. Open Notepad as admin. Right-click Notepad and choose Run as administrator.
2. Go to File > Open and paste this path:

C:\Windows\System32\drivers\etc\hosts

Look for any line that references the domain you're trying to reach. If you see something like 127.0.0.1 example.com, delete that line. Also remove anything that looks odd—random IPs with domain names you don't recognize. Save the file and try the site again.

Fix 4: Reset the network stack

If all else fails, a network reset will clear out every network setting, including winsock (the Windows socket API). This is a nuclear option but works wonders.

1. Open Terminal as admin.
2. Run these commands one by one:

netsh winsock reset
netsh int ip reset
ipconfig /flushdns

Restart your PC. Your network adapters will reinstall automatically, and you might need to reconnect to Wi-Fi. This kills most persistent DNS issues.

Alternative fixes if the main ones don't work

• Try a different browser — If Edge or Firefox loads the site fine, the problem is Chrome-specific. Clear Chrome's cache and cookies via Settings > Privacy and Security.
• Disable VPN or proxy — A VPN can hijack DNS. Turn it off and see if the site loads. Also check Windows proxy settings: Settings > Network & Internet > Proxy. Make sure it's off unless you're using one.
• Ping the domain — Open Command Prompt and type ping example.com. If it resolves to an IP, the site is up and the issue is browser-related.

Prevention tips

Once you fix the error, here's how to avoid it in the future:

• Keep your DNS set to a public server like Google or Cloudflare (1.1.1.1). Your ISP's DNS can be temperamental.
• Clear your DNS cache weekly if you work on networks that change often.
• Run a malware scan occasionally. Some viruses mess with DNS settings in Windows.
• If you use a VPN, make sure it's configured properly. Split tunneling or DNS leak protection can cause this error.

That's the full rundown. Start with flushing the cache, then switch DNS, and only then go nuclear with a network reset. I've fixed hundreds of these across Windows 10 and 11, and those steps cover practically every case.