DNS_PROBE_FINISHED_NXDOMAIN: What It Means, Why It Happens, and How to Fix It

If you’ve ever tried to open a website and Chrome (or another browser) shows DNS_PROBE_FINISHED_NXDOMAIN, you’re not alone. This issue is one of the most common DNS-related problems and it usually means your device can’t translate a domain name (like example.com) into an IP address.

In this article, you’ll learn what the dns_probe_finished_nxdomain error is, what causes it, and the most reliable steps for a dns_probe_finished_nxdomain fix—from quick browser checks to deeper DNS troubleshooting.

What is the DNS_PROBE_FINISHED_NXDOMAIN error?

NXDOMAIN stands for “Non-Existent Domain.” In simple terms, your DNS resolver is responding with: “I can’t find that domain.”

So the dns_probe_finished_nxdomain error happens when:

The domain truly doesn’t exist (typo, expired domain, wrong TLD), or
Something on your device/network/DNS resolver is preventing a correct DNS lookup.

Common causes of DNS_PROBE_FINISHED_NXDOMAIN

Here are the most frequent reasons behind this error:

Typos or wrong domain
- goggle.com instead of google.com, or wrong suffix like .co vs .com.
DNS cache problems
- Your device, browser, or router is holding an outdated or incorrect DNS record.
Broken/slow DNS resolver
- Your ISP DNS may be failing, filtering, or returning incorrect results.
VPN, proxy, security software interference
- Some tools intercept DNS and can misroute or block lookups.
Misconfigured local network
- Bad DNS settings, corrupted Winsock/adapter settings, or a router glitch.
Domain/DNS misconfiguration (website owner side)
- Missing A/AAAA record, incorrect nameservers, broken DNSSEC, or recent changes not yet propagated.

DNS_PROBE_FINISHED_NXDOMAIN fix: Step-by-step solutions

Work through these in order—most users fix it within the first few steps.

1) Confirm the domain actually exists

Before changing anything:

Try the site on another device (phone on mobile data is ideal).
Check if other websites work normally.

If only one domain fails everywhere, it may be an owner-side DNS issue.

2) Restart the basics (fastest win)

Restart your browser
Restart your PC
Restart your router/modem (power off 10–15 seconds)

This clears many temporary DNS/network states.

3) Clear the browser DNS cache (Chrome/Chromium)

Chrome keeps its own DNS cache.

Open: chrome://net-internals/#dns
Click Clear host cache
Then open: chrome://net-internals/#sockets
Click Flush socket pools
Restart the browser

This is a classic dns_probe_finished_nxdomain fix for Chrome users.

4) Flush your operating system DNS cache

Windows

Open Command Prompt as Administrator and run:

ipconfig /flushdns

(Optional deeper reset)

netsh winsock reset
Restart the PC

macOS

In Terminal:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux (depends on what you use)

Try one of these:

sudo resolvectl flush-caches (systemd-resolved)
Restart NetworkManager: sudo systemctl restart NetworkManager
Or restart systemd-resolved: sudo systemctl restart systemd-resolved

5) Change DNS servers (high success rate)

Switching to a reliable public resolver often resolves dns_probe_finished_nxdomain error issues immediately.

Good options:

Cloudflare: 1.1.1.1 and 1.0.0.1
Google DNS: 8.8.8.8 and 8.8.4.4

Set them on your device or (better) on your router so everything uses them.

Tip: After changing DNS, flush DNS cache again and reopen the browser.

6) Disable VPN/Proxy temporarily

If you use a VPN or proxy:

Disconnect it
Try the site again

Some VPNs push custom DNS that can return NXDOMAIN for blocked domains or due to resolver issues.

7) Check your hosts file (important)

A modified hosts file can “override” DNS.

Windows: C:\Windows\System32\drivers\etc\hosts
macOS/Linux: /etc/hosts

Look for any lines containing the domain you’re trying to visit and remove them (carefully). If you see many suspicious entries, that’s a red flag for adware/malware.

8) Reset your router DNS / network settings

If multiple devices on the same network get the error:

Set router DNS to Cloudflare or Google
Reboot router
If needed, “Forget” Wi-Fi network and reconnect

If you’re the website owner: Fix NXDOMAIN at the source

If visitors are reporting DNS_PROBE_FINISHED_NXDOMAIN, your DNS might be broken. Check:

Domain registration is active (not expired)
Nameservers match what your DNS provider expects
You have correct A/AAAA records for the hostname (@ and/or www)
DNS changes have propagated (can be minutes to 48 hours depending on TTL and resolver caching)
DNSSEC is either correctly configured or disabled (misconfigured DNSSEC can break resolution)