DroidCrunch
  • About
  • Blog
  • Categories
    • Automation
    • Tech
    • SEO
    • WordPress
    • Software
    • Hosting
    • Proxy
  • AI
    • AI Writing
    • AI Image
    • AI Tool
    • AI Video
  • Deals
  • Contact
Subscribe
No Result
View All Result
DroidCrunch
  • About
  • Blog
  • Categories
    • Automation
    • Tech
    • SEO
    • WordPress
    • Software
    • Hosting
    • Proxy
  • AI
    • AI Writing
    • AI Image
    • AI Tool
    • AI Video
  • Deals
  • Contact
Subscribe
DroidCrunch

DNS_PROBE_FINISHED_NXDOMAIN: What It Means and 8 Fixes That Work 2026

Lokesh Kapoor by Lokesh Kapoor
November 22, 2026
3
0

DNS_PROBE_FINISHED_NXDOMAIN means your browser asked for a website’s IP address and got back one answer: that name doesn’t exist. Your internet works. That one name didn’t resolve.

The fix is usually quick: check the spelling, clear your DNS cache or switch DNS servers.

Sometimes, though, the answer is true. We queried names that don’t exist through Cloudflare, Google and Quad9, and each reply came with a timer.

For a subdomain you add a minute too late, that timer reads 30 minutes. Flushing your laptop won’t beat it.

What DNS_PROBE_FINISHED_NXDOMAIN actually means

Every web address has to be turned into an IP address before your browser can connect. That job belongs to DNS, the internet’s address book, and the server doing the lookup for you is called a resolver.

NXDOMAIN is short for “non-existent domain”. It’s the resolver’s way of saying it checked with the servers in charge of that name and they have no record of it.

The long name is Chrome’s. When a lookup fails, Chrome runs a quick test of its own, the DNS probe, to work out whether your DNS is broken in general or only for this one site. “Finished NXDOMAIN” means the probe passed: lookups work, and this particular name came back as not found.

Other browsers say the same thing with friendlier words:

  • Edge shows the same DNS_PROBE_FINISHED_NXDOMAIN code, because it’s built on Chromium.
  • Firefox says “Hmm. We’re having trouble finding that site.”
  • Safari says it “can’t find the server”.

So what’s broken? One of three things. The name is wrong, something on your side is giving a stale or false answer, or the domain really has no records right now.

We triggered NXDOMAIN on purpose: here’s what came back

We asked the three biggest public resolvers about names we knew didn’t exist, using dig over DNS over HTTPS. Then we read the one line most guides skip: the SOA record that rides along with every NXDOMAIN answer.

Our NXDOMAIN test Bash
$ dig +https @1.1.1.1 droidcrunh.com A
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51158
;; AUTHORITY SECTION:
com.  900  IN  SOA  a.gtld-servers.net. nstld.verisign-grs.com. 1795346893 1800 900 604800 900

$ dig +https @1.1.1.1 droidcrunch.con A
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13715
;; AUTHORITY SECTION:
.  86400  IN  SOA  a.root-servers.net. nstld.verisign-grs.com. 2026112200 1800 900 604800 86400

The status line is the verdict. The last number in the SOA line is how many seconds every resolver may remember that verdict. That’s called negative caching, and it’s why a fix on the server side doesn’t show up instantly.

Name we looked upWho said noStatusCached for
droidcrunch.con (wrong ending)The root serversNXDOMAIN86,400 seconds (24 hours)
droidcrunh.com (typo in the name)The .com serversNXDOMAIN900 seconds (15 minutes)
A made-up subdomain of droidcrunch.comOur Cloudflare nameserversNXDOMAIN1,800 seconds (30 minutes)
droidcrunch.comOur Cloudflare nameserversNOERRORResolves normally
Queried through Cloudflare 1.1.1.1, Google 8.8.8.8 and Quad9 9.9.9.9. The cache time is the last field of the SOA record sent back with each answer.

Google and Quad9 gave the same verdicts and the same timers. The one difference proves the point: Quad9 had already cached the .con answer, so its timer read 3,287 seconds instead of a fresh 86,400. It was counting down.

That agreement tells you something useful.

If a name fails on all three, it’s not your resolver. It’s the domain.

Here’s the case that catches site owners. You open a new subdomain in the browser before its DNS record exists. The resolver gets NXDOMAIN and keeps it for up to 30 minutes on a Cloudflare zone. You add the record, refresh, and still see the error.

Nothing is wrong with the record. The old “doesn’t exist” answer just hasn’t expired yet.

NXDOMAIN negative cache times: 24 hours for a wrong ending, 15 minutes for a .com typo, 30 minutes for a new Cloudflare subdomain
Times come from the SOA record sent back with each NXDOMAIN answer. A resolver that already holds the answer counts down from there.

Real-world tip: a broken domain isn’t always NXDOMAIN. We also queried dnssec-failed.org, a test domain kept broken on purpose, and Cloudflare returned SERVFAIL with the note “DNSKEY Missing”. With DNSSEC checking switched off, the same name resolved fine. If dig says SERVFAIL, your fix is in the DNSSEC settings, not the records.

First, find out if it’s you or the site

Open the same address on your phone, with Wi-Fi switched off so it uses mobile data.

Does it load? Then the site is fine and the problem sits on your computer or your network. Start with fix 2 below.

Same error on the phone too? Then ask a public resolver directly. Open Command Prompt on Windows or Terminal on a Mac and run:

Ask a public resolver Bash
# Windows, Mac or Linux
nslookup the-site-you-want.com 1.1.1.1

# Mac or Linux, shorter answer
dig @1.1.1.1 the-site-you-want.com | grep status

“Non-existent domain” or NXDOMAIN from 1.1.1.1 means the internet at large can’t find that name either. No setting on your laptop will change that. Skip to the site owner section, or wait for the owner to fix it.

Is DNS_PROBE_FINISHED_NXDOMAIN your device or the site: test on mobile data, then ask 1.1.1.1
Two checks tell you which side to fix before you change any settings.

8 fixes for DNS_PROBE_FINISHED_NXDOMAIN, in the order to try them

They’re ordered from the fastest check to the most disruptive. Test the site after each one. The first four cover the common causes and change nothing permanent.

Fix DNS_PROBE_FINISHED_NXDOMAIN step by step

Reload the page after each step before moving on.

  1. 1
    Step 1 of 8

    Check the spelling and the ending

    Look for a dropped letter or a wrong ending like .con or .cmo. A wrong ending is the worst typo to make, because the root servers say no and resolvers may cache that answer for 24 hours.

  2. 2
    Step 2 of 8

    Restart your router and reconnect

    Switch Wi-Fi off and on, or restart the router. Routers keep their own DNS cache, and a restart clears it along with any lookup that got stuck.

  3. 3
    Step 3 of 8

    Clear Chrome's host cache

    Open chrome://net-internals/#dns and click Clear host cache. Then open chrome://net-internals/#sockets and click Flush socket pools, and reload the page.

  4. 4
    Step 4 of 8

    Flush your computer's DNS cache

    Windows, macOS and Linux each keep answers for a while. Run the command for your system from the box below, then reload. This doesn’t touch your settings.

  5. 5
    Step 5 of 8

    Switch to a public DNS server

    Your ISP’s resolver may be slow or filtering. Set 1.1.1.1 and 1.0.0.1 (Cloudflare) or 8.8.8.8 and 8.8.4.4 (Google) in your network adapter’s DNS settings on Windows or Mac, or on the router to cover every device.

  6. 6
    Step 6 of 8

    Check your hosts file

    Open C:\Windows\System32\drivers\etc\hosts on Windows or /etc/hosts on Mac and Linux. A line with the site’s name overrides DNS. Delete it if you didn’t add it on purpose.

  7. 7
    Step 7 of 8

    Turn off the VPN, proxy and DNS filters

    Disconnect the VPN, disable any proxy and pause DNS-based ad blockers. On Android, set Private DNS back to Automatic. If the site loads, the tool’s DNS was the problem.

  8. 8
    Step 8 of 8

    Reset the network stack

    On Windows, run the release, renew and winsock reset commands from the box below, then restart. On a Mac, renew the DHCP lease in your network’s TCP/IP details. Do this last, because it drops your connection.

The flush commands for fix 4, by system:

Flush DNS and reset Bash
# Windows (Command Prompt)
ipconfig /flushdns

# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Linux with systemd-resolved
resolvectl flush-caches

# Windows network reset for fix 8 (run as administrator, then restart)
ipconfig /release
ipconfig /renew
netsh winsock reset

Common mistake: switching DNS servers before flushing. Your computer can keep serving the stale answer it already cached, so the new server never gets asked. Flush first, then switch, then test.

What if a VPN is involved? Most VPN apps send your lookups through their own DNS servers while connected, so a filtering or broken VPN resolver shows up as this error. Our guide to how a VPN works explains where those lookups go. A proxy can do the same thing, and proxy vs VPN covers which one handles DNS.

Fixing NXDOMAIN on your own website

If the public resolvers say your domain doesn’t exist, the fix lives at your registrar or DNS host. Work through these in order.

The domain expired or was put on hold

An expired domain, or one on a registry hold, gets pulled from its TLD’s zone. Every lookup then returns NXDOMAIN, whatever your records say. Log in to your registrar, check the domain status and renew it.

Our guide to how web hosting works explains which bill covers the domain and which covers the server. Those are often two separate renewals.

The nameservers point at the wrong place

After a move to a new host or to Cloudflare, the registrar has to list the new nameservers. If it still lists the old provider, and you’ve deleted the zone there, the lookup reaches servers that no longer know your domain.

Check with dig NS yourdomain.com +short. Those names should match the DNS host where you edit your records.

The record was never created

This one is easy to miss on new subdomains. The root domain works, but shop.yourdomain.com returns NXDOMAIN because nobody added an A or CNAME record for it. The www version needs its own record too.

Add the record in your DNS zone, then wait out the negative-cache timer from the table above before deciding it didn’t work. On Hostinger, the DNS zone editor lists every record on one screen, so a missing subdomain is easy to spot. We moved 20 sites there, and our Hostinger review covers how its domain and DNS management held up.

You moved DNS but left DNSSEC switched on

If you enabled DNSSEC with your old DNS host and moved, the registrar may still hold the old DS record. Validating resolvers then refuse the answers, which is exactly the SERVFAIL we saw on dnssec-failed.org. Remove the old DS record at the registrar, or add the new one your DNS host gives you.

Expert take: NXDOMAIN is a DNS problem, so it never reaches your server. If the name resolves and you still get an error page, you’re dealing with a server error instead. A 502 Bad Gateway or a 504 Gateway Timeout means DNS worked and the server behind it failed.

Mistakes that keep the error coming back

  • Editing the hosts file and forgetting it. A line you added for testing a migration overrides DNS for that name until you delete it.
  • Typing a Private DNS hostname on Android with a typo. Every site then fails on that phone, while the rest of your devices work. Set it back to Automatic to test.
  • Assuming “propagation” when it’s caching. A record you just added isn’t spreading anywhere. Resolvers are holding an old “not found” answer until its timer runs out.
  • Blaming the browser. If dig and nslookup fail too, reinstalling Chrome won’t help. The lookup fails below the browser.

Is DNS_PROBE_FINISHED_NXDOMAIN a virus or a sign I’ve been hacked?

Almost never. It’s a lookup that came back “not found”. The one exception: some malware edits the hosts file to block security sites. If antivirus and update sites fail with this error while others load, open your hosts file, delete lines you don’t recognise and run a malware scan.

Why does the site load on my phone but not on my computer?

On mobile data, your phone uses your carrier’s resolver and its own cache. Your computer may be holding a stale answer, a hosts file entry, a VPN’s DNS or your router’s DNS. That points to your side, so work through fixes 2 to 7 on the computer.

Is DNS_PROBE_FINISHED_NXDOMAIN the same as ERR_NAME_NOT_RESOLVED?

They describe the same failure: the name didn’t resolve to an IP address. Chrome shows the DNS_PROBE version after its own check confirms the rest of your DNS works. The fixes are identical, so start with the spelling and your DNS cache either way.

Why do I only get the error on one Wi-Fi network?

That network’s router or DNS server is answering differently. Office, school and parental-control networks often filter domains, and some filtering resolvers reply “not found” for blocked names. Quad9 does this for domains it flags as malicious. Test on mobile data or with 1.1.1.1 to confirm.

How long does a new DNS record take to start working?

On a resolver that never looked the name up, it works straight away. If someone queried it before the record existed, that resolver keeps the not-found answer until its negative cache runs out: 30 minutes on our Cloudflare zone, 15 minutes for an unregistered .com name.

Can an ad blocker cause DNS_PROBE_FINISHED_NXDOMAIN?

A DNS-level blocker can. Pi-hole, NextDNS, AdGuard DNS and router filters answer blocked names with “not found” or an empty address. If one site fails on every device in your home, check the blocker’s query log and allowlist the domain. Ordinary browser extensions rarely cause it.

Does this error hurt my website’s SEO?

Only if search engines hit it too. When Googlebot can’t resolve your domain, it can’t crawl a single page, and Search Console reports DNS errors. A short blip is harmless. An expired domain left unresolved for days can start dropping pages from the index, so renew and recheck quickly.

The bottom line

DNS_PROBE_FINISHED_NXDOMAIN is a lookup that came back “not found”. On your side, the order is simple: check the spelling, restart the connection, clear the browser and system DNS cache, then switch to a public resolver like 1.1.1.1.

If Cloudflare’s resolver gives NXDOMAIN too, stop changing your laptop. The domain itself has no record, an expired registration or the wrong nameservers.

For your own site, fix the record, then give the negative cache its 15 to 30 minutes. If a 503 shows up once the name resolves, our guide to the 503 Service Unavailable error picks up from there.

Summarize this article with AI

Get the key points in seconds. Pick an assistant and it opens in a new tab, ready to go.

ChatGPTClaudePerplexityGoogle AIGrokMistral

Opens in a new tab. Nothing is shared until you pick an assistant.

Share4Tweet2Share1Share
Previous Post

Semrush Coupon Codes (2026): Discount & Latest Offers

Next Post

Royal MCP Review 2026: We Deleted a Post to Test the Undo

Lokesh Kapoor

Lokesh Kapoor

I am Lokesh Kapoor who loves to write blogs, create videos and watch sci-fi movies on Netflix and Jio Cinema. DroidCrunch is my first love and a crucial part of my life.

Related Posts

Crocoblock review title card with a JetEngine modules dashboard and 23 JetPlugins

Crocoblock Review 2026: Pros, Cons & Pricing From a Live Site

What is DNS title card: a domain name being translated into an IP address

What Is DNS? How the Domain Name System Works 2026

November 22, 2026
299
WordPress.com coupon codes: an order summary showing a 3-year Personal plan at $99 instead of $324 billed monthly

WordPress.com Coupon Codes (2026): Discount & Offers

November 19, 2026
305
WordPress statistics data report: a laptop dashboard showing CMS market share, version charts and a world map

WordPress Statistics 2026: Real Market Share, Versions and Plugins (Plus Our 2,000-Site Scan)

November 15, 2026
299
Load More

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

I agree to the Terms & Conditions and Privacy Policy.

DroidCrunch

Tested first. Then written.

Independent software reviews since 2016. Search the archive, or start with a topic.

WordPressAI toolsHostingVPNSEO
  • 620+reviews, comparisons and guides
  • 242product reviews
  • 36topics covered
  • 2016publishing since
home

An independent tech blog and YouTube channel. We use every tool before we rate it, and we always tell you the catch.

Topics

  • WordPress
  • AI tools
  • Hosting
  • SEO
  • VPN
  • Proxies
  • Automation

Company

  • About DroidCrunch
  • Editorial policy
  • Affiliate disclaimer
  • Write for us
  • Contact

Explore

  • All articles
  • Reviews
  • Deals and coupons
  • Black FridayLive
  • Facebook group
  • Help and support

Recently scored

  • Royal MCP80%
  • WPVibe76%
  • Zapier82%
  • Apify81%
All reviews

Reader-supportedWhen you buy through our links, we may earn a commission at no extra cost to you. It never changes our verdicts. Read our affiliate disclaimer.

© 2026 DroidCrunch. Independent since 2016.

  • Privacy policy
  • Terms
  • Cookie policy
  • Your GDPR rights
  • RSS
Back to top

Welcome Back!

Login to your account below

Forgotten Password?

Retrieve your password

Please enter your username or email address to reset your password.

Log In

Add New Playlist

No Result
View All Result
Subscribe
  • About
  • Blog
  • Categories
    • Automation
    • Tech
    • SEO
    • WordPress
    • Software
    • Hosting
    • Proxy
  • AI
    • AI Writing
    • AI Image
    • AI Tool
    • AI Video
  • Deals
  • Contact

© 2026 DroidCrunch - Best Place for Tech NomadPrivacy PolicyTerms & ConditionsCookie PolicyGDPR RightsAffiliate Disclosure

DroidCrunch Giveaway

Amazon Gift Card worth $15

Participate now and get a chance to become a lucky winner to receive the reward.​

Join Giveaway