The DNS_PROBE_FINISHED_NXDOMAIN error means your browser cannot find the IP address of a domain. In simple terms, the domain does not resolve in DNS. Chrome usually shows it under the heading “This site can’t be reached” with the text “…’s server IP address could not be found.”
This error can be caused by a typo, DNS misconfiguration, an expired domain, or local network problems. Fixing it usually takes just a few steps once you identify the source.
Quick Fix
- Check that the domain is spelled correctly (no typos, correct extension).
- Restart your router and computer.
- Flush your DNS cache and Chrome’s host cache (
chrome://net-internals/#dns). - Switch to Google DNS (8.8.8.8 / 8.8.4.4) or Cloudflare DNS (1.1.1.1 / 1.0.0.1).
- Disable your VPN, proxy, or DNS-filtering software and test again.
- Check the hosts file for entries that override the domain.
- If you own the site: check the domain’s expiry date, nameservers, and A record.
If the site opens on mobile data or another network, the problem is local. If it fails everywhere, the problem is the domain’s DNS.
What Is DNS_PROBE_FINISHED_NXDOMAIN?

DNS (Domain Name System) translates domain names like example.com into server IP addresses. Before your browser can connect to a website, it asks a DNS resolver for that address.
If this process fails, the browser shows NXDOMAIN (Non-Existent Domain). “DNS_PROBE_FINISHED” means Chrome ran its own DNS check after the failure, and “NXDOMAIN” is the answer it got: the DNS system says this name does not exist.
This means either:
- The domain does not exist, is misspelled, or has expired
- DNS records are missing or broken (for example, no record for the
wwwsubdomain) - Your device, VPN, or DNS server is returning a wrong or stale answer
Firefox, Safari, and Edge show the same problem with different wording. Closely related Chrome messages are ERR_NAME_NOT_RESOLVED and Server IP Address Could Not Be Found.
Why This Error Happens

A DNS lookup goes from your device to a resolver, then to the root servers, the TLD servers (for example .com), and finally the domain’s authoritative nameservers. NXDOMAIN can come from any break in that chain.
Incorrect Domain Name
A simple typo in the URL can trigger NXDOMAIN. Check the spelling, the extension (.com vs .co), and any subdomain.
Domain Not Registered or Expired
If the domain is not active, DNS resolution fails completely. An expired domain or one placed on hold is removed from the TLD zone, so every resolver returns NXDOMAIN.
DNS Records Missing
If A records or nameservers are not configured, the domain cannot resolve. A common case: example.com works but www.example.com does not, because there is no A or CNAME record for www.
DNS Propagation Delay
After changing nameservers or records, it can take time for updates to spread. Resolvers can also cache the NXDOMAIN answer itself for a while (negative caching). See DNS propagation: how long it takes and how to speed it up.
Local DNS Cache Issues
Your device and browser may store outdated DNS records.
Hosts File Entries
The hosts file overrides DNS. A leftover entry from development, an ad blocker, or malware can send the domain to the wrong place or block it.
Firewall, Antivirus, or DNS Filtering
Security software and filtering DNS services may block DNS requests or answer NXDOMAIN for domains they flag.
VPN, Proxy, or Secure DNS Issues
Some VPN services use unstable DNS servers, and Chrome’s Secure DNS may use a different provider than the rest of your system.
Step-by-Step Fixes

1. Check the Domain Name
Make sure the URL is correct. Even a small typo can cause NXDOMAIN. Type the address manually instead of using an old bookmark or autocomplete suggestion, and try it with and without www.
2. Test Another Network or Device
Open the site on your phone using mobile data. If it loads, the problem is your device, router, or ISP DNS. If it fails everywhere, skip to step 10.
3. Flush DNS Cache
This removes outdated DNS records.
Windows (Command Prompt as administrator):
ipconfig /flushdns
Mac (Terminal):
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Linux (systemd-resolved):
resolvectl flush-caches
4. Clear Chrome’s Host Cache
Chrome keeps its own DNS cache. Open chrome://net-internals/#dns and click Clear host cache. Then open chrome://net-internals/#sockets and click Flush socket pools. Reload the page.
5. Change DNS Servers
Switch to a reliable DNS provider.
- Google DNS: 8.8.8.8 / 8.8.4.4
- Cloudflare DNS: 1.1.1.1 / 1.0.0.1
On Windows: Settings → Network & internet → your connection → DNS server assignment → Edit. On macOS: System Settings → Network → your connection → Details → DNS. This often fixes the error instantly. If DNS problems persist, see DNS Server Not Found.
6. Check Chrome’s Secure DNS Setting
In Chrome, go to Settings → Privacy and security → Security → Use secure DNS. Try switching it off, or select a provider such as Google or Cloudflare. If the site starts working, the previous Secure DNS provider was the problem.
7. Restart Network Devices
Restart your router and computer. This clears temporary network problems and the router’s own DNS cache. On Windows, netsh winsock reset followed by a restart also resets the network stack.
8. Check the Hosts File
The hosts file can override DNS. Make sure the domain is not listed there.
- Windows:
C:\Windows\System32\drivers\etc\hosts(open Notepad as administrator) - macOS and Linux:
/etc/hosts(edit withsudo nano /etc/hosts)
Remove any line containing the domain, save, and flush DNS again.
9. Disable VPN, Proxy, or Security Software
Turn off the VPN and any proxy, and temporarily pause antivirus web protection or DNS filtering. If the site then works, add an exception instead of leaving protection off.
10. Check Domain DNS Records (Website Owners)
If you own the website:
- Verify the A record (and AAAA, if you use IPv6) points to your server IP
- Make sure
wwwhas an A or CNAME record - Check that the nameservers at the registrar match your DNS provider
- Confirm the domain has not expired and is not on hold
If the domain resolves but shows the wrong site, see Domain Not Pointing to Hosting.
Advanced Troubleshooting
Check Domain Status
Use a WHOIS or RDAP lookup to confirm the domain is registered and active. Look at the expiry date and the status codes. clientHold or serverHold means the domain is not published in DNS, which causes NXDOMAIN for everyone until the registrar resolves it.
Test DNS Resolution
Use the command:
nslookup yourdomain.com nslookup yourdomain.com 8.8.8.8
“Non-existent domain” means DNS is not resolving the name. If it fails with your default DNS but works with 8.8.8.8, your local or ISP resolver is the problem.
On macOS or Linux, dig gives more detail:
dig yourdomain.com dig NS yourdomain.com +short dig +trace yourdomain.com
Check the status: field. NXDOMAIN means the name does not exist; NOERROR with no answer means the name exists but has no record of that type. +trace shows whether the chain breaks at the TLD (often an expired domain) or at your nameservers (missing record).
Use Online DNS Tools
Check whether the domain resolves globally. Mixed results (some locations return an IP, others NXDOMAIN) usually mean a recent change is still propagating.
Check Hosting Configuration
Make sure your hosting account is active and the A record matches the IP your host gave you. See also Website Not Working After DNS Change.
Does NXDOMAIN Affect SEO?
Yes, if it affects everyone and not just your device. If your domain cannot resolve, search engines cannot access your site. If it lasts, this leads to deindexing, traffic loss, and ranking drops. Fix DNS issues as quickly as possible.
How to Prevent DNS Errors
- Use reliable DNS providers
- Turn on auto-renew and monitor domain expiration
- Double-check DNS changes before saving them
- Keep backups or exports of your DNS zone
When to Contact Support
Contact your provider if:
- DNS changes do not propagate after 48 hours
- The domain shows no records or the wrong nameservers
- The domain status shows a hold you did not expect
- You cannot access DNS settings
Your registrar or hosting provider can verify configuration issues. If only you are affected, contact your ISP.
Frequently Asked Questions
It means the domain cannot be resolved by DNS. The DNS system answered that the name does not exist, so the browser has no IP address to connect to.
No. It is a DNS resolution issue. The web server is never contacted. The cause is either your device or network DNS, or the domain’s own DNS records or registration.
Yes, when the problem is your ISP or router DNS. Switching to Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1) often fixes it. It will not help if the domain itself has expired or has no DNS records.
Your computer is using a different DNS path: a stale DNS cache, a hosts file entry, a VPN, Chrome Secure DNS, or different DNS servers. Flush DNS, clear Chrome’s host cache, and check the hosts file.
Record changes often show up within minutes to a few hours, depending on TTL. Nameserver changes can take up to 24-48 hours. Resolvers may also keep a cached NXDOMAIN answer until it expires.
Yes. Some security software, parental controls, and VPNs filter DNS or use unreliable DNS servers. Disable them temporarily to test, then add an exception or change their DNS settings.
Related DNS Errors
If you’re dealing with DNS issues, these guides can help you fix similar problems:
- DNS Server Not Found — Fix Guide
- ERR_NAME_NOT_RESOLVED — How to Fix
- Server IP Address Could Not Be Found
- This Site Can’t Be Reached
- Domain Not Pointing to Hosting — DNS Setup Fix
- DNS Propagation — How Long & Fix
- Website Not Working After DNS Change
Summary
DNS_PROBE_FINISHED_NXDOMAIN means the browser cannot resolve the domain name into an IP address.
First check the spelling and test on another network. If the site works elsewhere, flush your DNS and Chrome’s host cache, switch DNS servers, check the hosts file, and rule out the VPN or security software. If it fails everywhere, check the domain’s registration status, nameservers, and A records with WHOIS, nslookup, and dig.
Main Error Hub
For a full list of DNS, SSL, server, and WordPress issues, see the complete website error guide.
Hi, I’m Alex — the person behind ErrorRescue.
I’ve been working with websites, servers, and hosting for over 8 years. Most of my experience comes from troubleshooting real problems on WordPress sites, VPS and shared hosting environments, and Cloudflare setups. I’ve dealt with everything from SSL certificate failures and DNS misconfigurations to 504 timeouts, memory exhaustion errors, and Cloudflare 5xx issues.
I started ErrorRescue because I got tired of seeing generic, outdated, or incomplete error guides. My goal is to write clear, practical fixes based on what actually works in production — not just theory. Every guide here is tested against common server setups (Apache, NGINX, Cloudflare, and popular WordPress stacks).
When I’m not fixing sites, I’m usually reviewing new hosting configurations or updating existing guides so they stay accurate.
