DNS_PROBE_FINISHED_NXDOMAIN
Resolve DNS_PROBE_FINISHED_NXDOMAIN by checking domain records, nameservers, resolver cache, DNS propagation, and browser/network settings.
Start here
Quick Answer
Check the exact hostname, then compare another network and public resolver. If only one device fails, clear local DNS and browser cache. If every resolver returns NXDOMAIN, the domain owner must fix nameservers, records, or registration state.
NXDOMAIN vs 404
DNS_PROBE_FINISHED_NXDOMAIN means the resolver could not find a DNS answer for the hostname. It is not the same as a 404 Not Found, where the domain resolves and the server says the route is missing. Start with DNS only when the hostname itself fails to resolve.
Local cache vs authoritative DNS
If the domain works on one network but not another, compare recursive resolvers and flush local DNS cache with the resolver comparison guide. If the issue began after a hosting or nameserver change, audit authoritative NS, A, AAAA, and CNAME records with the DNS record audit guide.
Escalation details
Send support the domain, failing resolver, expected IP or target, nameservers, time of change, TTL, and example command output from nslookup or dig. Avoid changing records repeatedly before TTL windows expire.
Diagnosis
Symptoms
- Chrome shows DNS_PROBE_FINISHED_NXDOMAIN.
- Other domains may still work normally.
- Results differ between devices, networks, or resolvers when cache or propagation is involved.
Common causes
- Typo, missing subdomain, stale bookmark, or malformed copied URL.
- Local DNS cache, hosts file, VPN, router, or ISP resolver issue.
- Missing DNS record, wrong nameservers, expired domain, or incomplete DNS migration.
- DNSSEC or registrar configuration problem.
Diagnostic Checklist
- Check the full hostname, including subdomain.
- Compare another network and at least two recursive resolvers.
- Query authoritative nameservers if public resolvers disagree.
- Inspect registrar nameservers and DNS records for the domain.
Fixes
Flush local DNS and compare resolvers
- 10 minutes
- Risk: low
- Anyone
- Chrome, DNS
Separate local cache from authoritative DNS failure.
- Retry the exact hostname on another network.
- Flush OS DNS cache and restart Chrome.
- Compare answers from your resolver, 1.1.1.1, and 8.8.8.8.
- Disable VPN or proxy temporarily if it changes DNS.
The hostname resolves locally or you prove the failure is outside one device.
If every resolver returns NXDOMAIN, move to domain owner checks.
The browser should move past DNS to an HTTP response.
Restore DNS/VPN settings that were not involved.
Repair authoritative DNS records
- 15-30 minutes
- Risk: medium
- Site owner
- DNS provider, registrar
Fix domain-side records when NXDOMAIN happens for everyone.
- Confirm registrar nameservers point to the DNS provider you are editing.
- Check apex and www records.
- Restore missing A, AAAA, or CNAME records.
- Check domain expiration and DNSSEC DS records if enabled.
Authoritative nameservers return the expected record.
If DNSSEC is broken, disable or repair DS records at the registrar.
Query authoritative and public resolvers after the change.
Restore previous known-good records if the new zone is incomplete.
Platform notes
WordPress cannot fix NXDOMAIN by itself. Check the registrar, DNS zone, CDN hostname, and nameservers first.
FAQ
Is DNS_PROBE_FINISHED_NXDOMAIN a server error?
No. The browser could not resolve the hostname, so it usually did not reach the web server.
Can DNS propagation cause this?
Yes. Some resolvers may cache old or missing answers until TTL expires, especially during nameserver or record changes.
Review notes
- Last reviewed
- 2026-05-05
- Reviewed by
- FaultForge Editorial Team, Web operations reviewer
- Tested on
Chrome DNS error checks, Windows and macOS resolver commands, authoritative DNS lookups, and public recursive resolver comparison.