Fix DNS_PROBE_FINISHED_NXDOMAIN and Other Network Errors Fast

You're mid-Google search, or trying to load a work portal, and Chrome throws DNS_PROBE_FINISHED_NXDOMAIN at you. Or maybe it's ERR_INTERNET_DISCONNECTED, or Edge just says "This site can't be reached." I know this error is infuriating — especially when your Wi-Fi icon shows full bars and other devices on the same network are happily streaming Netflix.

Here's the thing: nine times out of ten, it's not your router. It's your computer's DNS resolver getting confused, a stale network stack, or a misconfigured adapter. Let's walk through the three most common causes, starting with the one that fixes it for most people.

Cause 1: Corrupted DNS Cache (The Usual Suspect)

Your computer caches DNS lookups to speed things up. When that cache goes bad — thanks to a router reboot, a VPN disconnect, or a flaky ISP — it keeps serving stale or broken IP addresses. That's when DNS_PROBE_FINISHED_NXDOMAIN pops up. You'll see this a lot after switching between home Wi-Fi and a corporate VPN, or after your ISP does maintenance at 2 AM.

The fix is dead simple. Flush the cache.

On Windows:

ipconfig /flushdns

You should see: Successfully flushed the DNS Resolver Cache. If you don't, open Command Prompt as Administrator first.

On macOS (Catalina and later):

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

On Linux:

sudo systemd-resolve --flush-caches

After flushing, restart your browser. Don't just close the tab — fully quit Chrome or Edge. I've seen people flush DNS, then wonder why it didn't work while the browser was still holding onto the old resolver state. Also, if you're on Windows and flushdns alone doesn't do it, run these two back-to-back:

ipconfig /release
ipconfig /renew

That forces your machine to grab a fresh IP and DNS server from your router. Works more often than people give it credit for.

Cause 2: Your DNS Server Is Down or Blocked

If flushing didn't fix it, your DNS resolver itself is probably the problem. Your ISP's default DNS servers go down more often than they'd like to admit. And some networks — hotel Wi-Fi, corporate guest networks, certain ISPs in regions with censorship — actively block or poison DNS queries.

Test it. Open Command Prompt and run:

nslookup google.com 8.8.8.8

If that returns an IP address but nslookup google.com (without the 8.8.8.8) fails, your DNS server is the culprit. Switch to a public resolver.

Windows: Control Panel → Network and Internet → Network Connections → right-click your adapter → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties → Use the following DNS server addresses:

• Preferred: 1.1.1.1 (Cloudflare — fastest in most tests)
• Alternate: 8.8.8.8 (Google)

macOS: System Settings → Network → your connection → Details → DNS → add 1.1.1.1 and 8.8.8.8.

I'm opinionated here: Cloudflare's 1.1.1.1 beats Google's 8.8.8.8 on latency in most of my tests, and their privacy stance is better. Use 8.8.8.8 as a backup only.

Heads up: if you're on a corporate network, don't change DNS servers without checking with IT. Split-horizon DNS setups will break internal sites if you point to public resolvers.

Cause 3: Broken Network Stack or Adapter Driver

You've flushed DNS. You've switched resolvers. Still nothing? Your TCP/IP stack or network adapter driver is likely corrupted. This shows up most after Windows updates (looking at you, KB5034441), after malware cleanup, or on machines running third-party "network optimizers" that muck with registry keys they shouldn't touch.

First, reset the network stack. Open Command Prompt as Admin and run these in order:

netsh winsock reset
netsh int ip reset
netsh advfirewall reset
ipconfig /flushdns

Reboot. Seriously — don't skip the reboot. Winsock reset doesn't take effect until restart.

If that doesn't fix it, update the adapter driver. Device Manager → Network adapters → right-click your Wi-Fi or Ethernet adapter → Update driver. Better yet, grab the driver straight from Intel, Realtek, or your laptop manufacturer's site. Windows Update often ships outdated drivers that cause exactly this kind of intermittent DNS failure. I've seen Intel AX201 cards on Windows 11 22H2 throw DNS errors until the driver was updated to version 22.190 or later.

Last resort: Windows Settings → Network & Internet → Advanced network settings → Network reset. This wipes all network config and reinstalls adapters. You'll lose saved Wi-Fi passwords, so have them handy.

Troubleshooting Quick Reference

One more thing: if you're on a public Wi-Fi network that requires a captive portal login, DNS errors are completely normal until you authenticate. Open http://neverssl.com in a browser to force the login page to appear. I can't tell you how many "network errors" I've "fixed" for friends by just telling them to open that site.