Your browser just loaded a blank grey page that says "This site can't be reached," and underneath it sits the real culprit: dns_probe_finished_nxdomain. Annoying? Definitely. Serious? Almost never. Nine times out of ten this is a failed DNS lookup, not a dead website — so you can usually fix it in under two minutes. Below are the fastest working fixes first, then the deeper causes, in the order our engineers actually check them. Real commands, real file paths, and a way to confirm the fix held.
Quick Answer: DNS_PROBE_FINISHED_NXDOMAIN means your device asked a DNS server for a site's IP address and got "no such domain" back — NXDOMAIN is short for non-existent domain. Usually it's a stale local DNS cache, a flaky resolver, or a typo, cleared in under two minutes by flushing DNS and switching to a public resolver like 1.1.1.1 or 8.8.8.8. Less often, the domain itself is expired or misconfigured at the host.
What DNS_PROBE_FINISHED_NXDOMAIN Actually Means
In the support tickets our team at Hostaccent handles, this error is far more often a client-side cache or DNS-propagation hiccup than a real website outage — which is good news, because those are the quickest fixes on this list.
Here's what's happening underneath. Every time you type an address, your device hands that name to a DNS resolver, which translates it into a numeric IP address. If the resolver replies "that name doesn't exist," Chrome shows DNS_PROBE_FINISHED_NXDOMAIN, Edge shows the same code, and Firefox phrases it as "We're having trouble finding that site." It's a naming failure, not a connection failure. If you want the full chain in plain English, Cloudflare has a solid breakdown of how DNS resolution works, and the formal definition of NXDOMAIN lives in the IETF's DNS terminology spec.
The practical takeaway: before you panic about your site being down, rule out your own machine first. That's where we start every time.
What Causes the dns_probe_finished_nxdomain Error (Ranked by Frequency)
From most to least common, here's what actually triggers it:
- Stale local DNS cache — your computer remembers an old, wrong answer.
- A flaky or misconfigured DNS resolver — usually your ISP's default DNS having a bad moment.
- A simple typo —
exmaple.cominstead ofexample.com. It happens more than anyone admits. - A hosts-file entry blocking or misdirecting the domain.
- VPN, proxy, or browser-extension interference.
- The domain is expired or unregistered — the name genuinely doesn't exist anymore.
- Wrong or missing DNS records at the host (no A record, broken CNAME).
- Recent nameserver change still propagating — the new records haven't reached your resolver yet.
Causes 1 through 5 are you (the visitor). Causes 6 through 8 are the domain owner. Across the sites we host at Hostaccent, the version that actually reaches a support ticket is almost always 6, 7, or 8 — because if it were a local cache, the visitor would've fixed it before contacting anyone. Keep that split in mind: it tells you whether to fix your machine or check your domain.
Client-Side Fixes: Flush DNS, Reset Chrome, and Switch Resolvers
Start here. These clear roughly 80% of cases verify and take two minutes.
1. Flush your DNS cache.
- Windows (Command Prompt as admin):
bash
ipconfig /flushdns ipconfig /release ipconfig /renew - macOS (Terminal):
bash
sudo dscacheutil -flushcache sudo killall -HUP mDNSResponder - Linux (systemd-resolved):
bash
sudo resolvectl flush-caches
2. Clear Chrome's own DNS cache. Chrome keeps a separate internal cache from your OS. In the address bar go to chrome://net-internals/#dns and click Clear host cache, then open chrome://net-internals/#sockets and click Flush socket pools. Reload the page.
3. Switch to a reliable public resolver. If your ISP's DNS is the problem, point your device at Cloudflare (1.1.1.1 and 1.0.0.1) or Google (8.8.8.8 and 8.8.4.4) instead. On Windows: Settings → Network → Adapter properties → IPv4 → enter the DNS addresses. On macOS: System Settings → Network → DNS. On Android/iPhone, set a Private DNS or change the Wi-Fi DNS.
Pro Tip: Restarting the router and your device clears DNS state on both sides at once. If you've already flushed three times and nothing changed, a 60-second power-cycle of the router often does what the commands couldn't — because the stale answer was cached upstream, not on your PC.
If the error vanishes after switching resolvers, your ISP's DNS was the culprit — leave it on 1.1.1.1 permanently and you'll likely never see this again.
Domain, Hosts File, and Browser Checks
Still stuck? Work through these before assuming it's the server.
Check the spelling. Sounds obvious — but type the address by hand, slowly. A single transposed letter produces this exact error because that domain really doesn't exist.
Inspect the hosts file. A stray line here forces a domain to a dead IP. Open and review:
- Windows:
C:\Windows\System32\drivers\etc\hosts - Mac/Linux:
/etc/hosts
Remove any line referencing the broken domain (unless you put it there on purpose for local testing), save, and flush DNS again.
Disable VPN, proxy, and extensions. A VPN or proxy can route your DNS through a server that returns NXDOMAIN. Turn it off and retry. Then test in an Incognito window — if the site loads there, a browser extension is interfering. Disable extensions one by one.
Test on another network. Switch from Wi-Fi to mobile data (or vice versa). If the site loads on a different network or a different device, the problem is isolated to your first setup — not the website.
Insider Insight: If the error hits every site, it's your DNS or network. If it hits only one site across multiple devices and networks, stop debugging your computer — the problem is on the domain/host side, and the next section is where you need to be.
Server-Side and DNS Record Fixes (When It's Not You)
If you own the domain and it fails everywhere, the name itself is the issue. Three things to check, in order.
1. Is the domain registered and paid? Run a WHOIS lookup. An expired or unregistered domain returns NXDOMAIN by definition — there's no record to resolve. Renew it (or register it), then wait for it to re-propagate. Before you buy or renew, it's worth knowing exactly what you're paying for; our domain and hosting buying guide covers the renewal-price traps that catch people out.
2. Are the nameservers correct? The domain must point to your host's nameservers at the registrar. Check with:
bashdig NS yourdomain.com nslookup -type=NS yourdomain.com
If the nameservers are blank or wrong, set them at your registrar to the ones your host gave you.
3. Do the actual records exist? Even with correct nameservers, a missing A record (for the root domain) or a broken CNAME (for www) produces NXDOMAIN on that hostname. Check:
bashdig A yourdomain.com dig www.yourdomain.com
Add the missing record in your control panel's DNS zone editor.
When we migrate a site to Hostaccent, the single most common cause of a post-move NXDOMAIN is exactly this — the nameservers were updated but the new A record wasn't created yet, so yourdomain.com resolves and www doesn't, or the reverse. Hostaccent's own stack runs Cloudflare in front of Nginx → Apache on NVMe SSD storage, and one quirk worth knowing: if a record is set to "DNS only" instead of proxied (or vice versa) by mistake, the site can resolve for some visitors and not others while caches catch up.
Pro Tip: After any nameserver or record change, expect propagation to take anywhere from a few minutes to 24–48 hours, governed by the record's TTL. Your fix may already be correct — a global propagation checker will show it spreading region by region before your own resolver catches up. Don't keep "fixing" something that's just propagating.
If this is bleeding into broader site problems — slow loads, timeouts, resource caps — those are separate issues worth ruling out. Our guides on diagnosing a slow WordPress site and the shared hosting resource limit exceeded error cover the next layer down.
How to Confirm the Fix Held and Stop It Recurring
Once the page loads, verify it properly rather than trusting one reload.
- Reload from a clean state: Incognito window plus a fresh DNS flush.
- Confirm the record resolves:
ping yourdomain.comordig A yourdomain.comshould now return an IP, not "NXDOMAIN." - Check from outside your network: load the site on mobile data or ask someone in another region. Consistent loads everywhere means propagation is complete.
To stop it coming back:
- Turn on domain auto-renew so an expiry never silently takes the name down.
- Keep DNS on a reliable resolver (
1.1.1.1) on your own devices. - Lower TTL before planned changes. Drop the record TTL to 300 seconds a day before you switch nameservers, so the new records propagate fast. Raise it back afterward.
- Document your DNS records so a missing A or MX entry doesn't surprise you later. (If you also run email on the domain, the MX records matter just as much — our guide to creating email with your own domain walks through those.)
You can sanity-check any DNS term you're unsure of against MDN's DNS glossary — it's a clean, vendor-neutral reference.
Reliable Hosting and DNS Without the Surprises
Most dns_probe_finished_nxdomain reports trace back to two avoidable things: a domain that quietly expired, or DNS records that were never set cleanly in the first place. Get those right once and the error mostly disappears from your life.
That's the boring reliability Hostaccent is built around — a UK-registered host (with a Bangladesh branch) running WHMCS, Cloudflare, Nginx → Apache and NVMe storage, with UK-based human support that checks your DNS zone with you when something looks off. If you're starting fresh and want the domain and hosting set up correctly from day one, a free domain bundled with hosting is a clean way to avoid the registrar-mismatch headaches that cause half these tickets. Plans start at $1.99/yr for the Economy tier. No pressure — fix your error first; the offer's here when you need it.
Frequently Asked Questions
Why does dns_probe_finished_nxdomain keep coming back?
A recurring dns_probe_finished_nxdomain usually means the underlying cause was never fixed — an unstable ISP resolver, a VPN that keeps reconnecting, or a domain whose records are intermittently wrong. Set your DNS to 1.1.1.1 permanently and verify your A and NS records are correct, not just temporarily flushed.
Is DNS_PROBE_FINISHED_NXDOMAIN a virus?
No. It's a standard DNS lookup failure, not malware. That said, some adware can hijack DNS settings or the hosts file and cause it. If you also see redirected searches or pop-ups, run a malware scan and check that your hosts file and DNS settings haven't been altered.
How do I fix "this site can't be reached" on my phone?
Toggle airplane mode on and off, then forget and rejoin the Wi-Fi network. On Android, set Private DNS to 1.1.1.1. On iPhone, change the Wi-Fi network's DNS to 8.8.8.8. If it works on mobile data but not Wi-Fi, the router or its DNS is the problem.
Does flushing DNS delete anything important?
No. Flushing the DNS cache only clears temporary address lookups your device stored. It removes nothing personal, no files, no passwords, and no browsing history. The cache simply rebuilds itself with fresh answers the next time you visit sites. It's completely safe to do as often as you like.
Why does only one website show the NXDOMAIN error?
If a single domain fails everywhere — across devices and networks — the problem is that domain, not you. It's likely expired, missing an A record, or pointing at the wrong nameservers. Run a WHOIS and dig A check on it to confirm before touching your own settings.
Can my hosting cause dns_probe_finished_nxdomain?
Yes — if the host's DNS zone is missing an A record, or nameservers were changed without updating the records, visitors get NXDOMAIN. On our side at Hostaccent, the first thing support checks on these tickets is whether the A record and nameservers actually match, since a mismatch after migration is the usual offender.
Last updated: June 2026 — by The Hostaccent Team.
Discussion
Have a question or tip about this topic? Share it below — your comment will appear after review.