Fix DNS_PROBE_FINISHED_NXDOMAIN: Why Your Site Can't Be Found
DNS_PROBE_FINISHED_NXDOMAIN means DNS says your domain does not exist. Learn how to tell a local glitch from a domain problem, and how to fix each one.
If your browser shows “This site can't be reached” with the code DNS_PROBE_FINISHED_NXDOMAIN, it asked DNS for your domain's address and got no usable answer. Usually the answer was clear: that name does not exist. DNS is the internet's address book. It turns a name like example.com into the numeric address of a server. The cause is almost always in one of two places: your own device or network, or the domain itself. This guide shows you how to tell which, how to check it, and how to fix it.
What the error actually means
NXDOMAIN is short for “non-existent domain”. It is a normal DNS reply, not a crash. A DNS resolver (the server that looks up names for you, usually run by your internet provider) asked around and was told the name has no entry.
Chrome, Edge, Brave and Opera show the code DNS_PROBE_FINISHED_NXDOMAIN, often under the line “example.com's server IP address could not be found”. Firefox and Safari word it differently, but they mean the same thing: the name lookup failed. Chrome shows the same code for some other failed lookups too.
First, find out whether the problem is only on your side or everyone sees it.
First test: is it only you?
Open the site on your phone with Wi-Fi turned off, so it uses mobile data. That puts you on a different network and a different resolver. Then use an online DNS checker, a free website that looks up your domain from servers in many countries.
- If the site loads on mobile data and the checker shows an address everywhere, the problem is on your computer or network. Start with the next section.
- If the checker shows NXDOMAIN or no address in many places, the problem is with the domain. Skip to the section on domain problems.
Fixes on your own device or network
Your computer and browser remember DNS answers for a while. This memory is called the cache. If it saved a bad answer, it can keep showing the error after the real problem is gone.
- Flush the DNS cache. On Windows, open Command Prompt and run
ipconfig /flushdns. On a Mac, open Terminal and runsudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. On Linux systems that use systemd-resolved, such as Ubuntu, runsudo resolvectl flush-caches. Chrome keeps its own cache too: openchrome://net-internals/#dnsand click “Clear host cache”. - Try a different DNS resolver. Your provider's resolver may be holding a stale answer. Switch to a well-known public resolver in your network settings and test again. Also check Chrome's “Use secure DNS” setting, which can use a different resolver from the rest of your computer.
- Restart the router and pause any VPN or DNS-based ad blocker.
Problems with the domain itself
If the checker shows NXDOMAIN from many places, the fault is in the domain's setup. These are the usual causes.
The domain expired or is on hold
When a renewal fails, the registrar (the company you bought the domain from) or the registry (which runs the domain ending, such as .com) can put the domain on hold. A domain on hold is taken out of DNS, so every lookup returns NXDOMAIN. Picture a small shop in Tirana: the renewal was charged to an expired card, the reminders went to an old inbox, and one morning the website and email both stopped working. Log in to your registrar, check the expiry date and status, and renew. A WHOIS lookup will show statuses such as clientHold or serverHold.
The nameservers are wrong
Nameservers are the servers that hold your domain's DNS records. Your registrar must point your domain to the right ones. This can break during a move to a new host: the nameservers are changed before the records exist at the new place, or a nameserver name has a typo. When we move a site for you, we test it on a preview link first and you switch DNS last, which avoids this gap.
An A or CNAME record is missing
An A record links a name to a server address, such as 192.0.2.10. A CNAME record points one name to another name. If www has no record at all, www.example.com does not exist, even when example.com works. Our help center shows how to manage these records in Plesk.
A new name is still cached as missing
Resolvers keep answers for a set time, called the TTL (time to live). They also keep “does not exist” answers. If a resolver asked for a name before you created it, it can repeat that answer for a while. Wait, then flush your own caches.
How to check with nslookup and dig
You don't need special software. nslookup works on Windows, macOS and most Linux systems. dig comes with macOS and many Linux systems.
nslookup example.comA healthy reply lists an address. On Windows, a failed lookup says “Non-existent domain”; on macOS and Linux it shows NXDOMAIN.
dig example.com A
dig www.example.com CNAME
dig example.com NSIn dig's output, find the status: line near the top. NOERROR means the name exists; NXDOMAIN means it does not. SERVFAIL means the lookup failed, for example because of a broken nameserver or a DNSSEC (DNS signing) error. The NS query shows which nameservers the domain uses, so you can compare them with the ones your host gave you.
Quick reference: symptom, cause, fix
| Symptom | Likely cause | Fix |
|---|---|---|
| Works on mobile data, not on your Wi-Fi | Cache, resolver or router | Flush the cache, switch resolver, restart the router |
| Fails on one computer only | VPN, secure DNS setting or browser cache | Pause the VPN, check secure DNS, clear Chrome's host cache |
| Site and email fail everywhere | Domain expired or on hold | Renew at the registrar and check the status |
| Fails everywhere after a host move | Wrong nameservers or missing records | Check the nameservers and the zone at the new host |
| example.com works, www does not | No A or CNAME record for www | Add the missing record |
| New subdomain fails for some people | Old “does not exist” answer still cached | Wait for it to expire, then flush caches |
When you want a second pair of eyes
The fix is often one record or one renewal. If you host with Zebra Hosting Cloud, send us a ticket or email with your domain and what you see. Real people answer in 17 languages, including Albanian, and we will help you find the cause. Looking for a host that works this way? See our hosting plans.