DNS_PROBE_FINISHED_NXDOMAIN: 12 Real Fixes That Work

You typed a URL, hit Enter, and Chrome slapped back DNS_PROBE_FINISHED_NXDOMAIN. It looks scary, but it's almost always a cache issue or a bad DNS server — not the website being down and not malware. This guide walks through every fix that actually works, in the order most likely to succeed.

Table of Contents

• What DNS_PROBE_FINISHED_NXDOMAIN actually means
• First: confirm the domain really exists
• Fix 1 — Flush DNS on Windows 11 and Windows 10
• Fix 2 — Flush DNS on macOS
• Fix 3 — Clear Chrome and Edge internal DNS
• Fix 4 — Change DNS to Cloudflare or Google
• Fix 5 — Restart your router (correctly)
• Fix 6 — Reset the Windows TCP/IP stack
• Fix 7 — Check the hosts file for hijacks
• Fix 8 — Android and iPhone fixes
• Fix 9 — Disable VPN, proxy, and pi-hole style filters
• Fix 10 — ISP resolver failure (last resort)
• Common mistakes and troubleshooting
• Security best practices
• FAQ

What DNS_PROBE_FINISHED_NXDOMAIN Actually Means

Every time you visit a website, your device asks a DNS resolver to translate the human-readable name (like digimetricshub.com) into an IP address. NXDOMAIN is the resolver's way of replying, 'I asked the authoritative servers, and no record exists for that name.' Chrome and Edge wrap that response in the DNS_PROBE_FINISHED_NXDOMAIN error page.

There are only three real root causes: (1) the name really doesn't exist (typo, expired domain), (2) your local device or router has cached a bad answer, or (3) the resolver your ISP hands you is broken and returning NXDOMAIN when it shouldn't. Every fix below targets one of those three.

First: Confirm the Domain Really Exists

Before you spend an hour flushing caches, verify the site actually has DNS records. Run a DNS Lookup against the domain — if authoritative servers reply with valid A or AAAA records, the site exists and your device is the problem. If the lookup itself returns NXDOMAIN, the domain is expired, misspelled, or was never registered.

Fix 1 — Flush DNS on Windows 11 and Windows 10

The Windows DNS Client Service (dnscache) keeps a small in-memory cache of recent lookups. Stale NXDOMAIN answers live there until you clear them.

Using Command Prompt

1. Press Windows key, type cmd, right-click Command Prompt, choose Run as administrator.
2. Type ipconfig /flushdns and press Enter.
3. You should see 'Successfully flushed the DNS Resolver Cache.'
4. Optionally run ipconfig /registerdns to re-register with your DHCP server.

Using PowerShell

PowerShell has a native cmdlet: Clear-DnsClientCache. Run it in an elevated window (Windows key, type powershell, Ctrl+Shift+Enter).

Fix 2 — Flush DNS on macOS

macOS uses mDNSResponder. Open Terminal and run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Enter your login password when prompted. There is no confirmation message — no news is good news.

Fix 3 — Clear Chrome and Edge Internal DNS

Chromium browsers keep their own DNS cache that survives Windows and macOS flushes. Type chrome://net-internals/#dns in Chrome (or edge://net-internals/#dns in Edge), click 'Clear host cache', then open a second tab and go to chrome://net-internals/#sockets and click 'Flush socket pools'. Close and reopen every browser window afterwards.

Fix 4 — Change DNS to Cloudflare or Google

If flushing didn't help, your resolver itself may be returning bad answers. Switch to a reliable public resolver:

• Cloudflare — 1.1.1.1 and 1.0.0.1 (fastest globally, privacy-focused)
• Google — 8.8.8.8 and 8.8.4.4 (extremely reliable, huge cache)
• Quad9 — 9.9.9.9 (blocks known malicious domains at the resolver level)

Windows

Settings → Network & Internet → your connection → Edit DNS server assignment → Manual → IPv4 On → paste the addresses above → Save. Reboot the browser.

macOS

System Settings → Network → select your connection → Details → DNS → click + and add both addresses → OK. macOS starts using them immediately.

Fix 5 — Restart Your Router (Correctly)

A quick reboot isn't enough — your router's DNS cache and DHCP leases survive short power blips. Unplug the router, wait a full 30 seconds so capacitors drain, then plug it back in. Give it 2 minutes to fully re-associate with your ISP before testing.

Fix 6 — Reset the Windows TCP/IP Stack

If flushing and DNS changes didn't help, corrupted network settings might be the culprit. In an admin Command Prompt, run these one at a time: netsh winsock reset, netsh int ip reset, ipconfig /release, ipconfig /renew, ipconfig /flushdns. Reboot the PC when done.

Fix 7 — Check the Hosts File for Hijacks

The hosts file overrides DNS. Malware, ad blockers, or old developer edits can point a domain to 0.0.0.0 or 127.0.0.1, which triggers NXDOMAIN-like errors in modern browsers. Open the file:

• Windows: C:\Windows\System32\drivers\etc\hosts (open Notepad as admin first)
• macOS / Linux: /etc/hosts (sudo nano /etc/hosts)

Remove any lines that reference the failing domain, save, then flush DNS again.

Fix 8 — Android and iPhone Fixes

Android

1. Toggle Airplane Mode on for 10 seconds, then off.
2. Forget your WiFi network and rejoin it.
3. Go to Settings → Network & Internet → Private DNS → set it to 1dot1dot1dot1.cloudflare-dns.com.
4. Clear Chrome cache: Settings → Privacy → Clear browsing data.

iPhone

Settings → Wi-Fi → tap the ⓘ next to your network → Configure DNS → Manual → add 1.1.1.1 and 8.8.8.8. Then restart Safari and Chrome.

Fix 9 — Disable VPN, Proxy, and Pi-hole Style Filters

VPNs and DNS-level ad blockers (Pi-hole, AdGuard Home, NextDNS) can return NXDOMAIN for blocked domains or fail entirely when their upstream is down. Temporarily disable them and retry. If the site loads, you've found the culprit — check your blocklists for an over-broad rule.

Fix 10 — ISP Resolver Failure (Last Resort)

If every device on every network at your home fails on the same domain, and the DNS Lookup tool shows the site resolves globally, your ISP's DNS is broken. Change your router's DNS to Cloudflare or Google (router admin panel → DHCP/DNS settings) so every device on your network bypasses the ISP resolver.

Common Mistakes

• Assuming NXDOMAIN means malware — it almost never does.
• Flushing Windows DNS but forgetting Chrome's internal cache.
• Editing the hosts file without admin rights — the save silently fails.
• Restarting the router by clicking 'Reboot' in the admin panel (many models don't drain caches) instead of unplugging.
• Setting only IPv4 DNS while IPv6 still uses the broken ISP resolver.

Troubleshooting Checklist

1. Does the site resolve on a public DNS Lookup? If no, the domain is the problem.
2. Do other sites work on your device? If no, resolver or router.
3. Does the site work on mobile data (WiFi off)? If yes, router or ISP.
4. Does it fail only in Chrome? Clear chrome://net-internals/#dns.
5. Did it start after installing a VPN or ad blocker? Disable it.

Security Best Practices

• Prefer DNS over HTTPS (DoH) or DNS over TLS (DoT) so your ISP can't tamper with responses.
• Change the default admin password on your router to prevent DNS hijacking malware.
• Use Quad9 (9.9.9.9) if you want automatic blocking of known malicious domains.
• Periodically audit your hosts file for lines you didn't add yourself.