DNS_PROBE_FINISHED_NXDOMAIN

The short version: Usually this is yours to fix, right on your machine. Flush the DNS cache (ipconfig /flushdns on Windows), repoint your resolver at Cloudflare 1.1.1.1 or Google 8.8.8.8, and restart the browser. But if the same error hits every device for one website, the domain or its DNS records are at fault, not you.

Key takeaways

• NXDOMAIN is DNS reply code 3 (RFC 1035). The resolver answered, and what it said was that the name has no record. This is a definitive 'the name does not exist' verdict, not a timeout and not a slow server.
• For a visitor, the fix is almost always on your own machine. Flush the DNS cache, point your resolver at 1.1.1.1 or 8.8.8.8, and reload.
• Want to know whose fault it is? Run nslookup yourdomain.com 1.1.1.1. An NXDOMAIN from a public resolver you never normally touch blames the domain's records or its registration. Get an IP instead and you were just looking at a stale local cache.
• Owners see this for three recurring reasons: the registration lapsed, an A/AAAA/CNAME record was deleted or mistyped, or new nameservers have not propagated.
• A lapsed domain or a vanished record hands NXDOMAIN to everyone at once. So the prevention play is external monitoring: resolve your hostname from outside and get warned before your visitors are the ones telling you.

Error type

DNS / browser error

Whose side

Usually your side; sometimes the website

Fix difficulty

Easy

Common cause

Domain name did not resolve to an IP

What does DNS_PROBE_FINISHED_NXDOMAIN mean?

Before your browser can load anything, the site's name has to become a numeric IP address, and the Domain Name System (DNS) does that translation. The code DNS_PROBE_FINISHED_NXDOMAIN is really two messages bundled together: DNS_PROBE_FINISHED says the lookup ran all the way to a result, and NXDOMAIN is shorthand for 'non-existent domain.' In other words, the answer came back, and the answer was that the name has no address.

Technically, NXDOMAIN is DNS response code 3, the 'Name Error' from the DNS standard (RFC 1035), with RFC 8020 clarifying what it implies for names beneath it. You get it when the queried name, and everything under it, simply is not in DNS: the domain was never registered, it expired, or it is missing the records that should point it at a server. There is a catch, though. Your own computer can manufacture the same response from stale or wrong DNS information it is holding, which is why so many of the fixes begin on your machine.

RCODE 3

The DNS response code (NXDOMAIN, 'Name Error') that triggers this message, defined in RFC 1035

~95 ms

Average global DNS lookup time, so a healthy resolution should answer almost instantly, not fail

24-48 hrs

How long new or changed DNS records can take to fully propagate worldwide

How the DNS_PROBE_FINISHED_NXDOMAIN error appears

The wording changes depending on your browser, device, or server. Here is how this error commonly shows up:

example.com

This site can't be reached

example.com's server IP address could not be found.

DNS_PROBE_FINISHED_NXDOMAIN

• DNS_PROBE_FINISHED_NXDOMAIN the DNS lookup finished and returned NXDOMAIN, meaning the domain does not exist
• Chrome: This site can't be reached, [domain] server IP address could not be found
• Edge: Hmm... can't reach this page, with DNS_PROBE_FINISHED_NXDOMAIN below
• Firefox: Hmm. We're having trouble finding that site (Server Not Found)
• Safari: Safari Can't Find the Server
• Android Chrome: This site can't be reached, the webpage might be temporarily down

NXDOMAIN vs related DNS errors

These Chrome error codes look similar but point at different failures, so matching the code to the cause saves time.

DNS commands for diagnosing an NXDOMAIN

Run these from a terminal to see what DNS actually returns and isolate a local cache problem from a real record problem.

Public DNS resolvers to switch to

If your ISP resolver returns NXDOMAIN for a name that genuinely exists, point your device or router at one of these instead.

What causes DNS_PROBE_FINISHED_NXDOMAIN?

• A typo in the address, or a domain nobody ever registered (or one that has since expired)
• Stale or corrupted DNS cache somewhere in the chain: your computer, your browser, or your router, all pointing at an old answer
• A misconfigured or unreachable DNS resolver, frequently a flaky ISP server
• A leftover or wrong line in your local hosts file overriding the real address
• A VPN, proxy, antivirus, or firewall rewriting or blocking your DNS requests
• Chrome's Secure DNS (DNS over HTTPS) routing through a provider that cannot resolve the name
• On the website's end: missing or wrong A, AAAA, or CNAME records, or nameservers that have not propagated

How to find the cause fast

1. Try the same address on a second device, and on mobile data rather than Wi-Fi. Works elsewhere? Then the problem lives on the first device or network, not the domain
2. Load a couple of unrelated websites. If they come up fine, your connection is healthy and only this one name is failing to resolve
3. Force a public resolver with nslookup yourdomain.com 1.1.1.1. 'Non-existent domain' is a real DNS problem; an IP means your local cache was stale
4. Scan the address bar for typos, then confirm the domain has not expired with any WHOIS or registrar lookup

Terminal

dig +short example.com# (no answer returned)nslookup example.com** server can't find example.com: NXDOMAIN# no DNS record; check spelling and registration

How DNS_PROBE_FINISHED_NXDOMAIN looks from the outside

Pulsetic hits your website from 15+ locations every 30 seconds, and its domain and DNS checks resolve your hostname from the outside, exactly the way a visitor's browser does. Lose an A, AAAA, or CNAME record, or let the domain lapse, and the lookup starts returning NXDOMAIN globally rather than on one laptop, with an alert reaching you by email, SMS, voice call, Slack, Discord, Telegram, or webhook within seconds. That outside view is the honest test. A clean Pulsetic check while your own browser keeps erroring points straight at your local cache or resolver, not your DNS records. One caveat: Pulsetic measures reachability from the outside, so it does not see CPU, memory, or disk on your server.

How to fix DNS_PROBE_FINISHED_NXDOMAIN

If you are a visitor

1. Re-read the address for typos, then reload
2. Power-cycle your router and modem: off for about 30 seconds, then back on
3. Flush your operating system's DNS cache using the commands above
4. Clear Chrome's own DNS cache. Open chrome://net-internals/#dns and click Clear host cache, then go to chrome://net-internals/#sockets and Flush socket pools
5. Switch your DNS server to Cloudflare (1.1.1.1) or Google (8.8.8.8) and reload
6. Release and renew your IP: on Windows run ipconfig /release then ipconfig /renew; on macOS renew the DHCP lease
7. Turn off any VPN, proxy, or antivirus web shield for a moment to rule out interference
8. Open your hosts file (C:\Windows\System32\drivers\etc\hosts on Windows, /etc/hosts on macOS and Linux) and delete any line for the affected domain
9. Disable Chrome's Secure DNS at chrome://settings/security (Use secure DNS) and try once more

If you run the website

1. Check at your registrar that the domain is registered and not expired, and renew it if it is
2. Make sure the nameservers shown at the registrar match the ones your DNS host expects
3. Confirm an A record (plus AAAA for IPv6) or a CNAME exists and points at the correct server IP or hostname
4. Just changed records or nameservers? Give propagation up to 24-48 hours and test with an external DNS lookup tool
5. Running a CDN or proxy like Cloudflare? Make sure its DNS record is fully set up, not stuck half-configured
6. Put external DNS and uptime monitoring in place so the next NXDOMAIN is caught from outside before any visitor hits it

On Windows

1. Open Command Prompt as administrator and run ipconfig /flushdns
2. Renew the address: ipconfig /release, then ipconfig /renew
3. Restart the DNS client with net stop dnscache followed by net start dnscache
4. Set DNS to 1.1.1.1 / 8.8.8.8 under Network adapter, IPv4 Properties

On macOS

1. In Terminal, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
2. Open System Settings, Network, your connection, Details, TCP/IP, and click Renew DHCP Lease
3. Add 1.1.1.1 or 8.8.8.8 under Network, DNS, DNS Servers
4. Open the hosts file with sudo nano /private/etc/hosts and clear out stale entries

On Linux

1. Flush the cache: sudo systemd-resolve --flush-caches (or sudo resolvectl flush-caches)
2. Test the lookup with dig yourdomain.com or nslookup yourdomain.com
3. Point DNS at 1.1.1.1 / 8.8.8.8 in your NetworkManager connection settings
4. Open /etc/hosts and delete any wrong mapping for the domain

On iPhone or iPad

1. Flick Airplane mode on and off, or restart the device, to clear the DNS state
2. In Settings, Wi-Fi, tap the (i) on your network, then Configure DNS, Manual, and add 8.8.8.8
3. Still stuck? Settings, General, Transfer or Reset iPhone, Reset, Reset Network Settings
4. Update the Chrome app and iOS, then reload the page

On Android

1. Restart the phone, or toggle Airplane mode, to drop the stale DNS cache
2. Under Settings, Network and internet, Private DNS, set it to dns.google or one.one.one.one
3. Alternatively long-press your Wi-Fi network, Modify, Advanced, and set DNS 1 to 8.8.8.8
4. Clear Chrome's cache under Settings, Apps, Chrome, Storage, and reload

Still not fixed? Next steps

• Still getting NXDOMAIN from a public resolver? Query the domain's own authoritative nameservers directly with dig @ns1.yourhost.com yourdomain.com. An answer there but NXDOMAIN everywhere else is a delegation or propagation problem at the registrar, not a missing record.
• When the authoritative server also says NXDOMAIN, the record really is gone. Re-add the A, AAAA, or CNAME at your DNS host, and double-check you edited the live zone rather than a draft or a leftover zone at some other provider.
• Turned on DNSSEC recently? Test with dig +cd yourdomain.com (checking disabled). If it only resolves with validation off, a broken DS or RRSIG chain is being read as a failure, so fix or strip the DNSSEC records.
• Once the records look right, confirm worldwide with a multi-location DNS propagation checker. One working resolver can easily hide a delegation that has not reached the rest of the internet.

Code & configuration

Copy-paste starting points. Replace example.com and the paths with your own, and test changes on staging before production.

Flush the DNS cache (per operating system)

Windows:  ipconfig /flushdns
macOS:    sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Linux:    sudo systemd-resolve --flush-caches  (or: sudo resolvectl flush-caches)

Switch to a public DNS resolver (Cloudflare or Google)

Cloudflare:  1.1.1.1  and  1.0.0.1
Google:      8.8.8.8  and  8.8.4.4

Set these in your OS network adapter / Wi-Fi DNS fields, then reload the page.

Confirm whether the domain really resolves

nslookup example.com
nslookup example.com 1.1.1.1   (force a public resolver)

A 'Non-existent domain' reply confirms NXDOMAIN; an IP address means your local cache was stale.

How to prevent DNS_PROBE_FINISHED_NXDOMAIN

When the trouble is on your side, a DNS flush clears it. But when your domain's records are wrong or its registration runs out, the page hands NXDOMAIN to everyone. Pulsetic checks your website from multiple locations every 30 seconds, and its domain monitoring flags DNS and expiry problems before they pull the website offline, alerting by email, SMS, voice call, Slack, Discord, Telegram, or webhook. It gauges availability from the outside, not your server's internals.

Learn how Pulsetic's domain monitoring detects this from the outside, across 15+ locations.