DNS_PROBE_FINISHED_NXDOMAIN: What It Means and How to Fix It

DNS_PROBE_FINISHED_NXDOMAIN is Chrome’s way of saying it asked the internet’s phone book for a domain’s address and got back “no such domain exists.” It’s not a server error, not a timeout, and not a permissions issue — it’s a failed name lookup, which narrows down the fix considerably.

What’s actually happening

Every time you type a web address, your browser asks a DNS resolver to translate that name into an IP address it can connect to. NXDOMAIN (“non-existent domain”) is the specific answer a DNS server gives when it has no record for that name at all — as opposed to a timeout, where it simply never answers.

That distinction matters: this error means a DNS server did respond, and its answer was “this doesn’t exist.” The cause is almost always one of three things:

1. A typo or an outdated address — the domain is misspelled, or it used to exist and doesn’t anymore.
2. A stale local DNS cache — your device or router cached an old (now-wrong) result and hasn’t refreshed it.
3. The domain’s own DNS records are broken or expired — if you own the site, its DNS zone or domain registration may have lapsed.

Step 1: Rule out the obvious

Before touching any settings, check the basics:

• Re-read the URL. A single dropped letter or wrong TLD (.cm instead of .com) produces exactly this error.
• Try the domain through a status checker. A server-side check resolves DNS independently of your device, so if it also can’t find the domain, the problem is with the domain’s DNS records, not your computer.
• Try a different device on a different network, or your phone on mobile data. If it resolves fine there, the issue is local to your original device or network.

Step 2: Fix it on your device (most common case)

If the domain resolves elsewhere but not for you, the fault is local. Work through these:

Flush the DNS cache.

• Windows: open Command Prompt as Administrator and run ipconfig /flushdns.
• macOS: run sudo killall -HUP mDNSResponder in Terminal.
• Chrome specifically keeps its own cache separate from the OS — visit chrome://net-internals/#dns and click Clear host cache.

Switch to a public DNS resolver. Your ISP’s default resolver can have outdated or broken records. Changing your device or router’s DNS to 1.1.1.1 / 1.0.0.1 (Cloudflare) or 8.8.8.8 / 8.8.4.4 (Google) frequently resolves this instantly, because you’re bypassing whatever is stale upstream.

Release and renew your IP. On Windows, run ipconfig /release followed by ipconfig /renew in an elevated prompt, then restart. This forces a fresh DHCP lease, which can include fresh DNS settings from your router.

Check for a VPN, proxy, or a modified hosts file. Any of these can silently redirect or block name resolution for specific domains. Temporarily disabling a VPN, or checking C:\Windows\System32\drivers\etc\hosts (Windows) or /etc/hosts (Mac/Linux) for a stray entry, rules this out.

Restart your router. It refreshes both your router’s own DNS cache and your device’s connection to it.

Step 3: If it’s your own site, check the domain itself

If the domain fails to resolve from everywhere — your device, another network, and an independent server check — the problem lives in the domain’s own configuration:

• Check whether the domain has expired. An expired registration stops resolving almost immediately. Your registrar’s dashboard will show the status plainly.
• Verify the nameservers are set correctly at your registrar and that your DNS zone actually has the A/AAAA records it needs.
• Give new DNS changes time to propagate. If you recently changed nameservers or records, NXDOMAIN can appear for a short window until the change fully propagates — usually under an hour, occasionally longer depending on TTLs.

Telling “my device” apart from “the domain itself”

The fastest way to split these two causes is an independent, server-side check: if our servers resolve the domain fine while your browser throws DNS_PROBE_FINISHED_NXDOMAIN, the issue is local — work through Step 2. If the independent check fails too, the domain’s DNS is genuinely broken or expired, and Step 3 is where to look. That one check saves you from flushing caches on a problem that was never yours to fix, or vice versa.

For the broader version of this question — not just this one error — see Is it down for everyone or just me?