DNS_PROBE_FINISHED_NXDOMAIN: What It Means and How to Fix It

• 26 June 2026
• by: Idris Mensah
• in: Web hosting
• Tags: dns error, NXDOMAIN, troubleshooting
• note: no comments

You typed an address, hit Enter, and instead of a website you got a blunt grey page: DNS_PROBE_FINISHED_NXDOMAIN. It looks alarming, but it is one of the most diagnosable errors on the web. My job here is to stay calm and isolate the cause, one layer at a time, until we know exactly where the breakdown is.

Let me walk you through what this error actually means, how to tell whether the problem is on your side or the site’s side, and the precise steps to fix it.

What does DNS_PROBE_FINISHED_NXDOMAIN actually mean?

Every website lives at a numeric IP address, but you type a human-readable name like `example.com`. The Domain Name System (DNS) is the lookup service that translates that name into the IP your browser can connect to. Think of it as the phone book of the internet.

NXDOMAIN is short for “Non-Existent Domain.” When your browser asked a DNS server “what is the IP for this domain?”, the answer came back: *there is no record for this name*. The browser finished its DNS probe (`DNS_PROBE_FINISHED`) and the result was a dead end (`NXDOMAIN`). In plain terms: the name could not be translated into an IP, so the connection never even started.

That is a crucial distinction. This is not a “the server is down” error or a “page not found” (404) error. The server was never contacted at all, because your browser never learned its address. The failure happened at the translation step.

Key Takeaways
• DNS_PROBE_FINISHED_NXDOMAIN means the DNS lookup found no record for the domain. The name could not be turned into an IP.
• It is a *resolution* failure, not a *connection* failure. The server was never reached.
• The fastest way to split the problem in half: test the same domain on a different network (like your phone’s mobile data).
• If it works elsewhere, the fault is your device or network DNS. If it fails everywhere, the fault is the domain’s DNS or registration.
• Common causes range from a simple typo to a stale local cache, a VPN, an expired domain, or a missing A record.

Is the problem me or the website?

This is the single most useful question to answer first, and most people skip it. There are two completely different sets of causes:

• Your side: a typo, a stale local DNS cache, a bad DNS resolver, a VPN, a misbehaving router, or your ISP’s DNS having a hiccup.
• The site’s side: an expired domain, missing or empty DNS records (no A record), broken nameservers, or a domain that was never set up correctly.

Here is the test that splits the entire problem in half. NXDOMAIN literally means “this name does not exist” *according to the DNS server that answered you*. So pull out your phone, turn off Wi-Fi, switch to mobile data, and load the exact same domain. Mobile data uses a completely different network and a completely different DNS resolver than your home or office connection.

• If the site loads on mobile data but not on your computer, the domain is fine. The problem is your device or local network DNS — flush your cache or switch resolvers (fixes 1 through 6 below).
• If the site fails on mobile data too, the domain itself is the problem — its DNS records are missing, its nameservers are broken, or the domain has expired (fixes 7 through 9, and the owner-side checks).

That one 20-second test tells you which half of this article to read.

How do I fix DNS_PROBE_FINISHED_NXDOMAIN as a visitor?

If the same domain works on another network, the issue is local. Work through these in order — they are sorted from quickest to most involved.

1. Double-check the spelling of the address. This sounds obvious, but it is the number one cause. `goggle.com`, `exmaple.com`, or a stray space at the end will all return NXDOMAIN because that exact name genuinely does not exist. Retype the address slowly.

1. Flush your local DNS cache. Your device remembers past lookups to save time, and a stale or poisoned entry will keep failing. Clearing it forces a fresh lookup.

On Windows, open Command Prompt and run: “` ipconfig /flushdns “`

On macOS, open Terminal and run: “` sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder “`

On Linux (systemd), run: “` sudo systemd-resolve –flush-caches “`

1. Clear Chrome’s internal DNS cache. Chrome keeps its own cache separate from the operating system. Paste this into the address bar:

“` chrome://net-internals/#dns “` Click Clear host cache, then open `chrome://net-internals/#sockets` and click Flush socket pools.

1. Restart your router. Your router caches DNS too, and a quick power cycle clears it. Unplug it, wait 30 seconds, plug it back in, and let it fully reconnect before testing again.

1. Disable your VPN or proxy temporarily. A VPN routes your DNS queries through its own servers, and if those misbehave you will see NXDOMAIN. Turn the VPN off, then reload the page. If that fixes it, switch VPN servers or check the VPN’s DNS settings.

1. Switch to a public DNS resolver. If your ISP’s DNS is failing, change your device or router to use a reliable public resolver. Google Public DNS is `8.8.8.8` and `8.8.4.4`; Cloudflare is `1.1.1.1` and `1.0.0.1`. After changing it, flush your cache again (step 2) so the new resolver is used immediately. For a deeper walkthrough, see our guide on clearing and refreshing your DNS.

If none of these help and the site also failed on mobile data, stop chasing your own device — the domain is the problem. Keep reading.

How do I fix it as the site owner?

If you own the domain and visitors (or you) are hitting NXDOMAIN everywhere, the fault is in your domain’s configuration or status. These checks tell you exactly which.

1. Confirm the domain has not expired. An expired domain gets pulled from DNS, and every lookup returns NXDOMAIN. Run a WHOIS lookup to see the registration and expiry dates:

“` whois example.com “` Look at the Registry Expiry Date and Status fields. If it has lapsed, renew it through your registrar immediately. Propagation back into DNS can take a few hours after renewal.

1. Check that your nameservers are set and reachable. If your domain points to nameservers that no longer exist or were never configured, no records can be served. Confirm the nameservers at your registrar match the ones your DNS host expects:

“` nslookup -type=ns example.com “`

1. Verify the A record actually exists. This is the most common owner-side cause. The A record is the entry that maps your domain to its server’s IP address. If it is missing or empty, the lookup returns nothing — NXDOMAIN. Query it directly:

“` nslookup -type=a example.com “` If no address comes back, log into your DNS management panel and add an A record pointing your domain (and the `www` host) to your server’s correct IP. To understand the full record set you should have in place, review our breakdown of essential DNS records and what each one does.

Once you have made a change, give it time. DNS updates do not apply instantly — they propagate, and your own stale cache can hide a fix you already made, so flush locally (step 2) before retesting.

Quick-reference: fixes by platform

Platform / location	Action	How
Windows	Flush OS DNS cache	`ipconfig /flushdns` in Command Prompt
macOS	Flush OS DNS cache	`sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`
Linux (systemd)	Flush OS DNS cache	`sudo systemd-resolve –flush-caches`
Chrome (any OS)	Clear browser DNS cache	`chrome://net-internals/#dns` → Clear host cache
Router	Clear cached lookups	Power cycle: unplug 30 seconds, reconnect
Any device	Switch resolver	Set DNS to `8.8.8.8` / `1.1.1.1`, then flush
VPN	Rule out tunnel DNS	Disable VPN, reload page
Domain owner	Confirm registration	`whois example.com` — check expiry and status
Domain owner	Confirm A record	`nslookup -type=a example.com` — must return an IP

What this error is *not*

It helps to rule out lookalikes so you do not waste time. DNS_PROBE_FINISHED_NXDOMAIN is specifically a name-resolution failure. If instead you are seeing 5xx pages, blank screens after the page started loading, or timeouts *after* a connection was made, you are dealing with a different layer entirely — those are server-side problems, not DNS ones. For that family of issues, see our guide to diagnosing server-side errors. And if you are simply unclear on how the whole lookup chain works in the first place, our explainer on what DNS is lays the groundwork.

---

Need DNS that just resolves? DarazHost provides reliable, fast DNS and clear record management so your visitors’ lookups resolve correctly the first time — no mysterious NXDOMAIN walls. And if you own a site that is hitting this error, our 24/7 support team helps you check your A records, nameservers, and domain status fast, so you spend minutes diagnosing instead of hours guessing.

---

Where DNS fits in the bigger picture

NXDOMAIN is really a story about the lookup chain: visitor types a name, a resolver translates it, and a connection is made to the server. When that translation fails, nothing downstream can work. To see how every piece of that journey fits together — resolvers, records, nameservers, and propagation — read the full pillar guide: Networking and DNS for Hosting: The Complete Guide to How Visitors Reach Your Server.

Frequently asked questions

Does DNS_PROBE_FINISHED_NXDOMAIN mean the website is down? No. It means the domain name could not be translated into an IP address, so your browser never actually reached the server. A down server returns a different kind of error (a timeout or a 5xx page) because the connection at least started. NXDOMAIN means the connection never began.

Why does the same site work on my phone but not my computer? Because your phone on mobile data is using a different network and a different DNS resolver. If the domain resolves there, the domain is fine — your computer’s local DNS cache or resolver is the culprit. Flush your cache and switch to `8.8.8.8` or `1.1.1.1`.

Will flushing my DNS cache delete anything important? No. The DNS cache is just a temporary list of recent name-to-IP lookups. Clearing it forces your device to fetch fresh answers. Nothing personal, no bookmarks, and no saved passwords are affected.

I own the domain and it just started showing NXDOMAIN. What changed? The two most common causes are an expired domain (check with `whois`) and a missing or deleted A record (check with `nslookup -type=a`). A nameserver change that has not finished propagating can also cause it temporarily. Verify those three in that order.

How long does it take for a fix to work? A local cache flush works instantly. A registrar renewal or a new A record needs time to propagate across DNS — usually minutes to a few hours, occasionally longer. Always flush your own cache after making a change, or you may keep seeing the old failure.