How to Fix the DNS_PROBE_FINISHED_NXDOMAIN Error (Step-by-Step)

You click a link, the page hangs for a moment, and Chrome hands you a blunt message: This site can’t be reached — DNS_PROBE_FINISHED_NXDOMAIN. It looks alarming, but in most cases it is a DNS lookup problem on your side, not a broken website. Below is what the error actually means and the fixes that resolve it, in the order worth trying.

What DNS_PROBE_FINISHED_NXDOMAIN means

Every domain name has to be translated into a numeric server address before your browser can connect. That translation is handled by DNS — the Domain Name System. The error breaks down like this:

• DNS — the Domain Name System, which maps names to addresses.
• PROBE — your browser’s attempt to perform that lookup.
• NXDOMAIN — short for non-existent domain: the lookup finished, and the answer was “no such name”.

In plain terms: your computer asked for the address of a domain and was told it does not exist. Firefox phrases the same thing as “We can’t connect to the server”, and Edge and Safari have their own wording, but the underlying cause is identical.

Why the error happens

The usual culprits, roughly in order of how often they turn out to be the problem:

• A simple typo in the address, or a domain that has expired or was never registered.
• A stale or corrupted DNS cache on your computer.
• Recent DNS changes that have not finished propagating yet.
• An unreliable DNS resolver from your internet provider.
• A VPN, proxy or security suite intercepting DNS queries.
• A leftover entry in your local hosts file.

Eight fixes, easiest first

1. Check the address, then confirm the domain exists

Before changing any settings, re-read the URL for a typo. If it looks right, check that the domain is actually registered and resolving — our free WHOIS lookup shows registration and expiry, and the DNS lookup tool shows whether it currently returns any records. If neither returns anything, the problem is the domain itself, not your machine.

2. Restart your router

Unplug it, wait about ten seconds, and plug it back in. This clears the router’s own DNS cache and re-establishes the connection to your provider. It is unglamorous, but it resolves a surprising share of cases.

3. Flush your local DNS cache

Your operating system remembers past lookups. If it cached a bad answer, it will keep serving it until the cache is cleared.

Windows — open Command Prompt as Administrator and run:

ipconfig /flushdns

You should see a confirmation that the DNS Resolver Cache was flushed.

macOS — in Terminal:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux (systemd) — in a terminal:

sudo resolvectl flush-caches

4. Release and renew your IP address

Still on Windows, follow the flush with a fresh lease from your router:

ipconfig /release
ipconfig /renew

5. Clear Chrome’s internal DNS cache

Chrome keeps its own cache, separate from the operating system. Visit chrome://net-internals/#dns, click Clear host cache, then reload the page. Testing the address in a private window (or a different browser) is also a quick way to rule out a browser-specific cache or extension.

6. Switch to a public DNS resolver

If your provider’s DNS is flaky, point your device at a public resolver instead. Two well-known options:

• Cloudflare — 1.1.1.1 and 1.0.0.1
• Google — 8.8.8.8 and 8.8.4.4

On Windows: Settings → Network & Internet → your connection → Edit DNS settings, then enter the addresses manually. On macOS: System Settings → Network → Details → DNS. Reload the site once saved.

7. Turn off VPN, proxy or antivirus temporarily

Security tools and VPN clients often route DNS through their own servers. Disable them briefly and reload the page. If the site loads, re-enable the tool and adjust its DNS settings rather than leaving protection switched off.

8. Check your hosts file

A manual entry here overrides DNS entirely and is easy to forget about. Look for lines mentioning the domain you cannot reach, and remove or comment them out.

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

If it is your own website

When visitors report this error on a site you run, the cause is usually one of these:

• The domain expired. Check the expiry date and renew it — this is the single most common reason a working site suddenly returns NXDOMAIN.
• Nameservers or A records are wrong or missing. Confirm the domain points at your hosting.
• A recent DNS change is still propagating. Updates can take from a few minutes to a few hours to reach every resolver.

Run your domain through our DNS lookup tool to see exactly which records are live right now. If you are new to records, what is DNS explains A, MX, CNAME and TXT in plain English.

In short

NXDOMAIN means the lookup completed and came back empty. Nine times out of ten it is a cached answer, a resolver problem or an expired domain — and the flush-and-switch-resolver steps above clear it in a couple of minutes. If the domain genuinely is not resolving, the fix belongs with whoever manages its DNS.