You type a web address, hit Enter, and instead of the page you get a blank screen with a cryptic line of text: DNS_PROBE_FINISHED_NXDOMAIN. It looks alarming, but in most cases it points to a simple, fixable problem with how your device translates a domain name into a server address.
In this guide we explain what the error actually means, what causes it, and how to fix it step by step — whether you are a visitor who just wants the page to load, or a site owner whose domain is showing the error to everyone.
Table of Contents
What does DNS_PROBE_FINISHED_NXDOMAIN mean?
Every website lives on a server with a numeric address called an IP address. Humans use names like copahost.com, but computers need the number behind that name. The system that translates one into the other is the DNS (Domain Name System) — think of it as the phone book of the internet.
When your browser cannot find a number for the name you typed, the DNS lookup comes back empty. The “NXDOMAIN” part literally stands for Non-Existent Domain. So the full message means: “I asked the DNS for the address of this domain, the lookup finished, and no such domain was found.”
The error is most associated with Google Chrome, which shows it alongside a “This site can’t be reached” message, but every browser hits the same underlying problem. Microsoft Edge phrases it as “Hmm… can’t reach this page,” while Firefox and Safari show their own variations.
What causes the error?
The causes fall into two groups: problems on your device or network (which only affect you), and problems with the domain or its DNS configuration (which affect every visitor). Telling these two apart is the single most useful diagnostic step, and we’ll come back to it in the comparison below.
Is it your device or the website? (quick comparison)
Before trying any fix, find out which side the problem is on. The fastest test: open the same address on a different network (for example, switch from Wi-Fi to mobile data) or use an online tool like DNS Checker. If the site loads elsewhere, the problem is local to you. If it fails everywhere, the domain itself is the issue.
Where is the problem coming from?
Does the site load on another network or device?
YES → your side
- Check the URL for typos
- Flush the DNS cache
- Switch to a public DNS (8.8.8.8)
- Disable VPN / antivirus briefly
- Renew your IP / restart router
- Reset Chrome flags
NO → site side
- Is the domain registered?
- Has it expired? Renew it
- Check the DNS records (A / CNAME)
- Confirm the nameservers
- Allow time for DNS propagation
- Contact your hosting provider
How to fix DNS_PROBE_FINISHED_NXDOMAIN (visitor side)
If the error only happens to you, work through these fixes in order — they are sorted from quickest to most involved.
1. Check the URL for typos
The simplest cause is a misspelled address or a pasted link that got truncated. Confirm the domain is spelled correctly before anything else.
2. Flush your DNS cache
Your operating system stores past lookups, and an outdated entry can point to nowhere. Clearing it forces a fresh lookup.
3. Change to a public DNS server
If your ISP’s DNS servers are unreliable, switching to a public resolver often fixes the error and can speed up browsing. Two popular free options:
4. Disable VPN, antivirus or firewall temporarily
Security software and VPNs can intercept or block DNS requests. Turn them off briefly and reload the page. If it works, re-enable the software and adjust its settings rather than leaving it off.
5. Renew your IP and restart your router
On Windows, run ipconfig /release followed by ipconfig /renew. If that doesn’t help, unplug your modem and router for about 30 seconds, then power them back on — this clears temporary network glitches.
6. Reset Chrome flags
Experimental Chrome settings can interfere with DNS resolution. Type chrome://flags in the address bar, click Reset all, and relaunch the browser.
How to fix it as a website owner
If your visitors report the error and the site fails on every network, the problem is with your domain or its DNS configuration. Check these in order:
Domain registration. Confirm the domain hasn’t expired. An expired domain stops resolving immediately. Renew it right away — most registrars offer a short grace period, but delays can add recovery fees.
DNS records. Make sure the domain has a valid A record (pointing to your server’s IP) or CNAME record. Missing records mean the browser has nowhere to connect.
Nameservers. Verify the domain points to the correct nameservers for your host. This is the most common culprit right after a migration to a new provider.
DNS Propagation. If you recently changed DNS records or nameservers, changes can take up to 24–48 hours to spread worldwide. Tools like DNS Checker show propagation status across regions.
A reliable host with correctly configured DNS prevents most NXDOMAIN errors from ever reaching your visitors. With Copahost, your domain and DNS records are set up correctly from the start, and support can help diagnose resolution issues quickly.
Frequently asked questions about DNS_PROBE_FINISHED_NXDOMAIN
What does DNS_PROBE_FINISHED_NXDOMAIN mean?
It means your browser asked the DNS for the IP address behind a domain name, the lookup completed, and no matching domain was found. “NXDOMAIN” stands for “Non-Existent Domain.” In short, the address you tried to reach could not be translated into a server, so the page cannot load.
Is DNS_PROBE_FINISHED_NXDOMAIN a virus?
No. It is a standard network error, not malware. It simply indicates a failed DNS lookup. That said, in rare cases aggressive antivirus software, a VPN, or malware that altered your network settings can trigger it — which is why temporarily disabling security software is one of the troubleshooting steps.
How do I fix DNS_PROBE_FINISHED_NXDOMAIN quickly?
Start with the fastest fixes: check the URL for typos, flush your DNS cache, and clear Chrome’s host cache at chrome://net-internals/#dns. If those don’t work, switch to a public DNS server like 8.8.8.8 or 1.1.1.1, disable any VPN or antivirus temporarily, and restart your router.
Why does the error happen only in Chrome?
Chrome keeps its own DNS cache, separate from your operating system, so a corrupted entry there can cause the error in Chrome even when other browsers work. Clearing Chrome’s host cache at chrome://net-internals/#dns usually resolves this specific case.
How do I know if the problem is my device or the website?
Open the same address on a different network or device — for example, switch from Wi-Fi to mobile data — or use an online tool such as DNS Checker. If the site loads elsewhere, the problem is on your device or local network. If it fails everywhere, the issue is with the domain or its DNS configuration.
Can an expired domain cause DNS_PROBE_FINISHED_NXDOMAIN?
Yes. When a domain expires or was never registered, there is no valid DNS record linking it to a server, so browsers return NXDOMAIN for everyone. If you own the domain, renew it immediately; registrars usually offer a short grace period before the name is released.
How long do DNS changes take to fix the error?
If you fixed DNS records or nameservers on a domain you own, the change can take up to 24 to 48 hours to propagate worldwide, though it is often much faster. Local fixes on your own device, such as flushing the cache, take effect immediately.
Conclusion
Despite its intimidating look, DNS_PROBE_FINISHED_NXDOMAIN is usually easy to solve. For visitors, it almost always comes down to a typo, a stale DNS cache, or an ISP resolver acting up — all fixable in a couple of minutes. For site owners, it points to the domain itself: registration, DNS records, or nameservers. The key is to first identify which side the problem is on, then apply the matching fix.
To learn more about how domains and resolution work behind the scenes, explore our related guides on DNS, hosting, and domains on the Copahost blog.
