DNS_PROBE_FINISHED_NXDOMAIN means your browser sent a DNS query for a domain name and received no result — the domain could not be found on any DNS server. In plain terms: your domain exists in a browser address bar but nowhere on the internet’s address book right now.
This error appears in Chrome, Edge, and other Chromium-based browsers. Firefox shows the same underlying issue as NS_ERROR_UNKNOWN_HOST. Safari displays it as “Safari Can’t Find the Server.”
What makes this error particularly frustrating is that it has at least five different root causes — and the fix for each one is completely different. Most guides only cover one or two. This guide covers all of them, starting with the most common and ending with the one that most developers miss entirely.
What DNS_PROBE_FINISHED_NXDOMAIN Actually Means
DNS (Domain Name System) translates human-readable domain names (like wpcodexplugins.com) into IP addresses that servers can route traffic to. When you visit a website, your browser queries a DNS server to look up that translation.
NXDOMAIN is the DNS response code for “Non-Existent Domain” — the DNS server was successfully reached, but it has no record of the domain you requested.
This is different from a timeout (where the DNS server does not respond at all) or a connection refused error (where the server is found but rejects the connection). NXDOMAIN specifically means: the DNS lookup completed, and the answer was “this domain does not exist.”
5 Causes of DNS_PROBE_FINISHED_NXDOMAIN and How to Fix Each One
Cause 1 — Local DNS Cache Serving a Stale Record
Your computer and browser cache DNS records locally to speed up repeat lookups. If a domain’s DNS was recently changed, your local cache may still hold the old (now invalid) record and return NXDOMAIN instead of querying fresh.
Fix — Flush your DNS cache:
Windows:
ipconfig /flushdnsOpen Command Prompt as Administrator and run the above command.
macOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderChrome browser DNS cache: Navigate to chrome://net-internals/#dns and click Clear host cache.
After flushing, close and reopen your browser and test the domain again.
Image alt text: “Windows Command Prompt showing ipconfig flushdns command to clear local DNS cache”
Cause 2 — DNS Propagation Still in Progress
DNS changes — including nameserver updates, A record changes, and domain transfers — do not take effect globally and instantly. Propagation can take anywhere from a few minutes to 72 hours depending on the TTL (Time to Live) value of the previous DNS records and the responsiveness of global DNS resolvers.
During propagation, some DNS servers around the world still return NXDOMAIN because they have not yet received the updated records.
Fix: Wait and verify propagation status. Use a DNS propagation checker to see which regions have received the updated records and which are still serving old data.
Check your domain’s current DNS propagation status with our free tool: DNS Checker Tool →
If propagation is the cause, the error will resolve itself as DNS records spread globally. Nothing else needs to be done.
Cause 3 — Incorrect or Missing DNS Records
If your domain’s DNS records were accidentally deleted, incorrectly configured, or never set up properly after a hosting migration, the domain will return NXDOMAIN even though it is registered and active.
Fix — Verify your DNS records:
- Log into your domain registrar or DNS management panel
- Confirm an A record exists pointing your root domain (
@) to your hosting server’s IP address - Confirm a CNAME record exists for
wwwpointing to your root domain or server - If using Cloudflare or another DNS proxy, confirm the records are active (orange cloud = proxied, grey cloud = DNS only)
Use the DNS Checker Tool to verify your records are resolving correctly from external DNS servers — not just inside your registrar dashboard.
Cause 4 — Expired Domain
When a domain registration expires, the registrar removes or suspends its DNS records. The domain immediately starts returning NXDOMAIN for all queries. This is one of the fastest and most disruptive causes — a site that was working perfectly at midnight can be fully unreachable by morning if the renewal was missed.
Fix:
- Log into your domain registrar account
- Check the expiry date on the domain
- If expired, renew immediately — most registrars offer a grace period (typically 30 days) before the domain enters redemption status
- After renewal, DNS records are usually restored within 1–4 hours
Prevention: Enable auto-renew on all domains and ensure your registrar has a current payment method on file.
Cause 5 — Domain serverHold Status (The One Most Guides Miss)
This is the cause that catches even experienced developers off guard — and it is the scenario most commonly behind “everything looks correct but the site still shows NXDOMAIN.”
serverHold is a domain status applied by the domain registry (not your registrar, not your host) that completely suspends DNS resolution for the domain. When serverHold is active:
- DNS will not resolve — the domain returns NXDOMAIN on every query
- Your website is completely inaccessible on all browsers and devices
- Email services connected to the domain stop functioning
- All DNS settings inside your hosting and registrar appear completely normal — because the block happens above those layers at the registry level
Common triggers for serverHold:
- Unverified domain contact details (ICANN requires verification of registrant email and contact information)
- Failure to respond to a domain verification email from your registrar
- Incomplete or incorrect WHOIS contact information
- Suspected fraudulent activity flagged by the registry
- Compliance or legal hold placed by the registry
How to identify serverHold: Run a WHOIS lookup on your domain and check the Domain Status field. If you see serverHold, that is the cause.
Domain Status: serverHold https://icann.org/epp#serverHoldUse our DNS Checker Tool to inspect your domain’s current status and DNS records from external resolvers.
Fix:
- Contact your domain registrar support and inform them the domain is showing serverHold status
- Ask them to investigate the reason and initiate removal
- Complete any required verification steps (email confirmation, WHOIS data correction)
- The registrar submits a request to the registry to remove the hold
- Once lifted, DNS resolution resumes — full propagation typically takes 1–4 hours
Quick Diagnosis Checklist
Not sure which cause applies to your situation? Work through this in order:
| Check | Tool | What to Look For |
|---|---|---|
| Is propagation complete? | DNS Checker Tool | Records resolving in most regions |
| Are DNS records correct? | Registrar DNS panel | A record, CNAME record present |
| Is the domain expired? | Registrar account | Expiry date, renewal status |
| Is serverHold active? | WHOIS lookup | serverHold in Domain Status field |
| Is local cache stale? | ipconfig /flushdns | Run flush, test again |
How Long Does It Take to Fix?
| Cause | Fix Time |
|---|---|
| Local DNS cache | Immediate after flush |
| DNS propagation | 1–72 hours (no action needed) |
| Incorrect DNS records | 1–4 hours after correcting records |
| Expired domain | 1–4 hours after renewal |
| serverHold | 4–24 hours after registrar removes hold |
Frequently Asked Questions
What does DNS_PROBE_FINISHED_NXDOMAIN mean?
It means your browser performed a DNS lookup for a domain name and received an NXDOMAIN response — the DNS server confirmed it has no record of that domain. The domain cannot be resolved to an IP address, so the browser cannot connect to the website.
Is DNS_PROBE_FINISHED_NXDOMAIN a problem with my internet or the website?
It can be either. If only one domain shows the error, the problem is with that domain’s DNS configuration or registration status. If multiple domains show the error, the issue may be your local DNS cache, your DNS resolver, or your network connection. Flushing your DNS cache (Cause 1 fix above) is always a safe first step.
How do I check if my domain has serverHold status?
Run a WHOIS lookup on your domain — search “WHOIS [yourdomain.com]” in Google, or use a dedicated WHOIS tool. In the Domain Status section of the results, look for the text serverHold. If present, contact your registrar immediately.
Can serverHold affect email as well as the website?
Yes. serverHold suspends all DNS resolution for the domain — including MX records that handle email routing. If your domain is under serverHold, email sent to addresses at that domain will bounce or queue undelivered until the hold is removed.
How do I prevent DNS_PROBE_FINISHED_NXDOMAIN from happening again?
Enable auto-renew on your domain registration, keep your registrar contact information and payment method current, respond promptly to any domain verification emails from your registrar, and set up monitoring alerts for domain expiry dates. Using a DNS monitoring tool to detect propagation issues early also helps catch problems before they cause visible downtime.
Does this error affect my WordPress SEO?
Yes. When your domain returns NXDOMAIN, search engine crawlers cannot access your site and will log crawl errors. Extended downtime (more than a few days) can result in ranking drops as Google begins to discount pages it cannot crawl. Fix the underlying cause promptly and use Google Search Console to request re-crawling of affected pages once the domain is resolving again.
Check Your DNS Health Right Now
If your site is showing DNS_PROBE_FINISHED_NXDOMAIN and you are not sure which cause applies, the fastest first step is a DNS lookup from an external server — not your local browser cache.
Use our free DNS Checker tool to instantly verify your domain’s DNS records, propagation status, and resolution from multiple global servers.
Check Your DNS Now — Free Tool →
More technical guides from WP Codex Plugins: How to Add a PHP Page to WordPress · WooCommerce CRM Automation Guide · All WordPress Free Tools
