Google Chrome Error Code ERR_DNS_PROBE_FINISHED_NXDOMAIN: How to Fix It

Easy 10-30 minutes Medium Severity Verified June 2026
Summarize with ChatGPTSummarize with ClaudeSummarize with Perplexity Add as Preferred Source on Google
Error Code
ERR_DNS_PROBE_FINISHED_NXDOMAIN
Brand
Google Chrome
Product Type
browser
Severity
Medium
DIY Difficulty
Easy
Estimated Fix Time
10-30 minutes
The ERR_DNS_PROBE_FINISHED_NXDOMAIN error in Google Chrome means the browser tried to look up a website's domain name but the DNS (Domain Name System) server returned 'Non-Existent Domain' — essentially, it could not find the address for the website you typed. This is almost always caused by a typo in the URL, a misconfigured DNS setting, a stale DNS cache, or a network configuration issue on your device or router. The good news is that this error is almost always fixable without any hardware changes or professional help.
Ad

Tools You'll Need

How to Fix Error Code ERR_DNS_PROBE_FINISHED_NXDOMAIN

  1. Check the URL for Typos

  2. Check Your Internet Connection

  3. Flush the DNS Cache on Your Device

  4. Clear Chrome's Internal DNS Cache

  5. Change Your DNS Server to a Public DNS

  6. Release and Renew Your IP Address

  7. Disable VPN or Proxy Settings

  8. Disable Antivirus or Firewall Temporarily

    Only disable antivirus or firewall software briefly for testing. Re-enable it immediately after. Never browse the internet for extended periods without active security software.

  9. Check and Edit the Hosts File

    Be careful not to delete default entries in the hosts file such as lines for 'localhost'. Only remove lines that reference the specific domain you are trying to fix.

  10. Reset Chrome Browser Settings

Ad

When to Call a Professional

If you have followed every step above and the error persists only for specific websites, the domain itself may truly not exist or may have expired — in which case there is nothing to fix on your end. If the error affects all websites on all browsers and devices on your network, contact your Internet Service Provider (ISP) as they may have a DNS or network outage in your area. If you suspect your computer is infected with malware that modified your hosts file or DNS settings, consider running a full scan with a reputable malware removal tool or consulting an IT technician.

Frequently Asked Questions

What does ERR_DNS_PROBE_FINISHED_NXDOMAIN mean in Chrome?
It means Chrome's DNS lookup for the website you tried to visit returned 'NXDOMAIN,' which stands for Non-Existent Domain. In plain terms, the internet's address book (DNS) could not find a listing for that domain name. This can happen due to a typo, an expired domain, a corrupted DNS cache, or a misconfigured network setting on your computer or router.
Why does ERR_DNS_PROBE_FINISHED_NXDOMAIN happen on only one website?
If the error only appears for one specific website, it usually means that website's domain does not exist, has expired, or was recently moved. It could also mean your local DNS cache or hosts file has an outdated or incorrect entry for that specific domain. Try flushing your DNS cache (Step 3) and clearing Chrome's internal DNS cache (Step 4) to resolve single-site issues.
Does ERR_DNS_PROBE_FINISHED_NXDOMAIN mean my internet is down?
Not necessarily. If only one or a few websites trigger this error while others load fine, your internet is working but there is a DNS resolution problem for those specific domains. If all websites fail to load with this error, your internet connection or DNS server may be down, and you should restart your router and contact your ISP if the issue persists.
Will changing my DNS to Google DNS (8.8.8.8) fix ERR_DNS_PROBE_FINISHED_NXDOMAIN?
Switching to Google's public DNS servers (8.8.8.8 and 8.8.4.4) or Cloudflare's DNS (1.1.1.1) often fixes this error when the problem is caused by a slow, unreliable, or misconfigured ISP DNS server. It is one of the most effective and permanent solutions for recurring ERR_DNS_PROBE_FINISHED_NXDOMAIN errors.
Can a VPN cause ERR_DNS_PROBE_FINISHED_NXDOMAIN in Chrome?
Yes. VPNs route your internet traffic through their own servers and can sometimes cause DNS leaks or conflicts that produce this error, especially if the VPN's DNS server is unresponsive or misconfigured. Try temporarily disabling your VPN and reloading the page. If the page loads without the VPN, contact your VPN provider for DNS configuration support.

Related Error Codes