DNS_PROBE_FINISHED_NXDOMAIN means Chrome queried the DNS system and received an “NXDOMAIN” response, which stands for “Non-Existent Domain.” In plain terms, the internet’s phone book has no listing for the domain you typed. Either the domain genuinely does not exist, your DNS cache holds a stale record, or your DNS server fails to resolve the address correctly.
This error blocks access to the entire website because without a valid IP address, Chrome cannot establish any connection. The NXDOMAIN response is definitive; your DNS server explicitly states the domain does not exist, rather than simply failing to respond. Here is how to determine whether the problem is real or fixable.
Check the Domain Name
Typos cause a large percentage of DNS_PROBE_FINISHED_NXDOMAIN errors. Verify you typed the URL correctly, paying attention to hyphens, dots, and TLD (.com vs .net vs .org). Try searching for the site name on Google instead of typing the URL directly. If the domain expired or the website shut down, no fix on your end will resolve this error.
Flush DNS Cache
Your computer caches DNS lookups to speed up repeat visits. If a domain recently changed its IP address or came back online after downtime, your cache might hold the old “does not exist” response. Open Command Prompt as administrator and run ipconfig /flushdns. Also clear Chrome’s internal DNS cache by navigating to chrome://net-internals/#dns and clicking “Clear host cache.”
Change DNS Servers
Your ISP’s DNS server may fail to resolve certain domains due to regional restrictions, outages, or filtering policies. Switch to Google Public DNS (8.8.8.8 and 8.8.4.4) or Cloudflare DNS (1.1.1.1 and 1.0.0.1). These public DNS services resolve more domains reliably than most ISP servers and update their records faster when domains change hosting providers.
Release and Renew IP Address
Open Command Prompt as administrator and run ipconfig /release followed by ipconfig /renew. This forces your network adapter to request fresh settings from your router, including updated DNS server assignments. On Mac, go to System Preferences > Network, select your connection, and click “Renew DHCP Lease.”
Restart DNS Client Service
The Windows DNS Client service sometimes hangs or corrupts its internal database. Open the Run dialog (Win+R), type services.msc, find “DNS Client,” right-click it, and select “Restart.” If the restart option is grayed out, open Command Prompt as administrator and run net stop dnscache followed by net start dnscache. This forces a fresh DNS resolution cycle.
Check Your Hosts File
Malware or leftover development configurations in your hosts file can redirect domains to nonexistent addresses. Open C:\Windows\System32\drivers\etc\hosts with administrator privileges and look for entries containing the domain you cannot reach. Remove any suspicious lines. The hosts file overrides DNS lookups, so an incorrect entry there triggers DNS_PROBE_FINISHED_NXDOMAIN regardless of your DNS server settings.
Frequently Asked Questions
What does NXDOMAIN mean technically?
NXDOMAIN stands for “Non-Existent Domain.” It is a DNS response code (RCODE 3) defined in RFC 8020. When a DNS server returns NXDOMAIN, it authoritatively confirms that the queried domain name does not exist in the DNS hierarchy. This differs from a timeout or SERVFAIL response, which indicate server problems rather than a missing domain.
Can a VPN fix DNS_PROBE_FINISHED_NXDOMAIN?
A VPN can fix DNS_PROBE_FINISHED_NXDOMAIN if your ISP blocks the domain or if regional DNS servers lack the record. VPNs route your traffic through servers in different countries with different DNS resolvers. However, if the domain genuinely does not exist, a VPN will not help because no DNS server anywhere will have a record for it.
