Have you ever tried to visit a website only to be greeted with an error message that says "This site can't be reached" followed by a cryptic error code called "DNS_PROBE_FINISHED_NXDOMAIN"? This frustrating issue can prevent you from accessing websites and can occur for many different reasons - from simple browser cache issues to complex DNS configuration problems.
In this comprehensive guide, we'll explain exactly what the DNS_PROBE_FINISHED_NXDOMAIN error is, what causes it, and provide 11 proven methods to fix it. Whether you're a website owner troubleshooting your own site or a user who simply wants to browse the internet without interruptions, this guide will help you resolve the DNS_PROBE_FINISHED_NXDOMAIN error quickly and efficiently.
DNS_PROBE_FINISHED_NXDOMAIN is an error that occurs when your web browser cannot locate the IP address associated with the domain name you're trying to visit. DNS (Domain Name System) is like the internet's phonebook - it translates human-readable domain names (like spidyhost.com) into machine-readable IP addresses (like 192.168.1.1) that computers use to identify each other on a network.
The "NXDOMAIN" part of the error specifically means "non-existent domain," indicating that the DNS server couldn't find the domain you're trying to reach.
The DNS_PROBE_FINISHED_NXDOMAIN error can occur for several reasons:
While we primarily focus on the DNS_PROBE_FINISHED_NXDOMAIN error in Google Chrome, this same issue appears differently in other browsers:
Browser | Error Message |
---|---|
Google Chrome | "This site can't be reached" with "DNS_PROBE_FINISHED_NXDOMAIN" |
Microsoft Edge | "Hmm... can't reach this page" with "DNS_PROBE_FINISHED_NXDOMAIN" |
Mozilla Firefox | "Hmm. We're having trouble finding that site." |
Safari | "Safari Can't Find the Server" |
Before diving into solutions, it's helpful to determine if the problem is with the domain itself, your browser, or your network configuration. Here are three effective ways to check the root cause:
One common reason for DNS_PROBE_FINISHED_NXDOMAIN errors is that the domain may be expired, unregistered, or on hold. To check this:
If the domain shows as "expired" or has hold statuses, contact the domain owner or registrar to resolve the issue.
Sometimes the error occurs because DNS changes haven't fully propagated through the internet. To check DNS propagation:
This method helps determine if the DNS_PROBE_FINISHED_NXDOMAIN error is specific to your network or browser:
Another way to isolate the problem is to check if the website can be accessed directly from its hosting server:
Now that we've identified potential causes, let's go through the solutions to fix the DNS_PROBE_FINISHED_NXDOMAIN error:
The DNS cache stores previous domain name lookups so your computer doesn't have to look them up again. However, if this cache contains outdated information, it can cause DNS errors.
ipconfig /flushdns
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Chrome has its own DNS cache separate from your operating system:
chrome://net-internals/#dns
in the address barThis process gives up your computer's current IP address and requests a new one, which can resolve network configuration issues.
ipconfig /release
ipconfig /renew
netsh int ip set dns
netsh winsock reset
Your Internet Service Provider's DNS servers might be experiencing issues. Switching to public DNS servers can often resolve the DNS_PROBE_FINISHED_NXDOMAIN error.
8.8.8.8
(Google's primary DNS)8.8.4.4
(Google's secondary DNS)Alternatively, you can use Cloudflare's DNS servers (1.1.1.1
and 1.0.0.1
) which are also fast and secure.
8.8.8.8
and 8.8.4.4
(Google) or 1.1.1.1
and 1.0.0.1
(Cloudflare)chrome://settings/security
in the address barThe DNS client service resolves and caches domain names. If it's not running correctly, you might encounter DNS errors.
This method is for Windows users only:
services.msc
, and press Enternet stop dnscache
net start dnscache
The hosts file on your computer can override DNS settings. If a domain is incorrectly listed there, it can cause DNS errors.
C:\Windows\System32\drivers\etc\
sudo nano /private/etc/hosts
Chrome's experimental features (flags) can sometimes interfere with proper DNS resolution.
chrome://flags
in the address barSecurity software can sometimes block certain domains or interfere with DNS resolution.
Windows:
macOS:
The process varies depending on your antivirus software. Generally:
Remember to re-enable your security software after testing!
For website owners, if your site uses a Content Delivery Network (CDN), it might be causing DNS resolution issues.
If you use Cloudflare:
Sometimes, simply resetting your networking equipment can resolve DNS issues:
If you're the domain owner and visitors are reporting DNS_PROBE_FINISHED_NXDOMAIN errors, check your domain's registration status:
If you've recently registered the domain, remember that DNS propagation can take up to 48 hours to complete worldwide.
If you're a website owner or administrator, you can check whether the issue is with DNS or the server itself:
If you manage websites, here are some preventative measures to avoid DNS_PROBE_FINISHED_NXDOMAIN errors:
The error indicates that the DNS probe (lookup) has finished but found that the domain doesn't exist (NXDOMAIN = Non-Existent Domain). This means your browser couldn't translate the domain name into an IP address needed to reach the website.
It can be either. The error could be caused by issues with your browser's cache, your computer's DNS settings, your router, your internet service provider, or the website itself. That's why we provide multiple troubleshooting methods.
Even if a website exists, you might get this error if:
Clearing browser data, particularly the DNS cache, can often resolve the issue. However, if the problem persists, you may need to try other methods like changing DNS servers or checking your network configuration.
Different DNS errors indicate different problems:
Yes, website firewalls like Cloudflare or Sucuri can sometimes cause DNS resolution issues, especially if they're misconfigured or if your IP address is blocked.
The DNS_PROBE_FINISHED_NXDOMAIN error, while frustrating, is usually fixable with the right approach. We've covered 11 different methods to resolve this error, from simple browser cache clearing to more advanced DNS configuration changes.
If you're experiencing this error as a user, start with the simpler solutions like flushing your DNS cache and restarting your network equipment. If you're a website owner dealing with reports of this error, check your domain registration status and DNS configuration.
Remember that DNS changes can take time to propagate worldwide, so some patience may be required when making configuration changes. If all else fails, don't hesitate to contact your internet service provider or hosting company for additional support.
By following the comprehensive troubleshooting steps in this guide, you should be able to resolve the DNS_PROBE_FINISHED_NXDOMAIN error and get back to browsing the internet without interruptions.
Have you encountered any other effective methods to fix the DNS_PROBE_FINISHED_NXDOMAIN error? Let us know in the comments below!
DevOps Engg
A metallurgist by education, tech enthusiast by passion. I've transformed my curiosity into expertise in web hosting, DevOps, and web development. With hands-on experience in Linux administration, cPanel, WordPress, and Node.js.
View more posts by Shaik VahidDiscover everything about web hosting in 2025. Learn about hosting types, costs, and features in this comprehensive guide that breaks down web hosting into simple terms for both beginners and experts.