You type a URL into Chrome, hit Enter, and instead of your page you get a stark white screen with the message DNS_PROBE_FINISHED_NXDOMAIN. NXDOMAIN stands for "Non-Existent Domain" — the DNS system looked up the hostname you requested and came back empty-handed. That does not necessarily mean the site is down. Nine times out of ten the problem is on your end: a stale cache, a misconfigured DNS server, a rogue VPN, or a router that has gone sideways. This guide covers every realistic cause and every fix, in order from fastest to most involved, so you can stop guessing and get back online.
What NXDOMAIN Actually Means
When a browser navigates to a URL it first asks a DNS resolver to translate the hostname (e.g., example.com) into an IP address. If the resolver returns an NXDOMAIN response — DNS response code 3 — it is formally declaring that the domain does not exist in any authoritative zone it can find. Chrome intercepts that response and surfaces it as DNS_PROBE_FINISHED_NXDOMAIN instead of showing a raw DNS error.
There are two very different root causes hiding behind the same error message:
- The domain genuinely does not exist — it was mistyped, it expired, or the DNS records were deleted by the registrar or host.
- Your local environment is broken — your DNS cache is poisoned or stale, your resolver is unreachable, a VPN is intercepting queries, or a hosts file entry is overriding the real record.
The fastest way to tell them apart is to check the domain from a different network or use an external tool. Use the DNS Lookup tool on this site to query the domain from multiple locations worldwide. If the domain resolves globally but not on your machine, the fix is local. If it fails everywhere, the problem is with the domain itself or its authoritative DNS.
Step 1: Confirm It Is Not a Typo or an Expired Domain
Before diving into network settings, look at the URL bar carefully. A single transposed character — gogole.com instead of google.com — returns a legitimate NXDOMAIN because that hostname does not exist. Check the spelling, clear it, and retype manually rather than relying on autocomplete.
If the URL is correct, check whether the domain registration has lapsed. Expired domains are removed from DNS within hours of expiry. Search the WHOIS record for the domain and look at the expiry date. If the domain belongs to you or your company and it expired, renew it immediately through your registrar — propagation back into the DNS tree typically takes 1–4 hours after renewal.
Step 2: Flush Your Local DNS Cache
Your operating system maintains a DNS cache to speed up repeated lookups. If a record was cached at the wrong time — perhaps during a DNS propagation window or right after a server migration — your machine may be serving a stale NXDOMAIN answer long after the real record exists. Flushing the cache forces a fresh lookup.
Windows 10 and 11
Open Command Prompt as Administrator, run the command above, and look for the confirmation: Successfully flushed the DNS Resolver Cache. Then restart the browser completely — do not just open a new tab.
macOS (Ventura, Sonoma, Sequoia)
Open Terminal, paste both commands separated by a semicolon, enter your password, and press Enter. There is no confirmation message on modern macOS — the silence means it worked.
Linux (systemd-resolved)
The statistics command lets you verify the cache was cleared — the current cache size should drop to zero or near zero.
Chrome Internal DNS Cache
Chrome maintains its own DNS cache separate from the OS. Even after an OS flush, Chrome may still serve the old answer. Navigate to the following address in the Chrome address bar and click Clear host cache:
While you are there, go to chrome://net-internals/#sockets and click Flush socket pools to clear any lingering TCP connections as well.
Step 3: Change Your DNS Server
Your ISP's default DNS servers are often the weakest link. They can be slow, temporarily down, or returning incorrect responses. Switching to a public resolver like Cloudflare (1.1.1.1) or Google (8.8.8.8) takes two minutes and is one of the most effective fixes for persistent NXDOMAIN errors.
Windows
Go to Settings > Network and Internet > Advanced network settings > Change adapter options. Right-click your active adapter, choose Properties, select Internet Protocol Version 4 (TCP/IPv4), click Properties, and enter:
Click OK, then repeat for IPv6 using 2606:4700:4700::1111 and 2606:4700:4700::1001.
macOS
Go to System Settings > Network, select your active connection, click Details, then the DNS tab. Remove existing entries and add 1.1.1.1 and 8.8.8.8. Click OK and then Apply.
Ubuntu / Debian
Find the DNS= line, uncomment it, and set:
Save the file and restart the resolver:
Step 4: Check and Reset Your Router DNS Settings
If multiple devices on the same network get NXDOMAIN errors for the same sites, the problem is almost certainly in the router. The router hands out DNS server addresses to all clients via DHCP. If those addresses are wrong or the router's own resolver is broken, every device on the network suffers.
Log into your router's admin panel. Common addresses:
- TP-Link: tplinkwifi.net or 192.168.0.1
- Netgear: routerlogin.net or 192.168.1.1
- ASUS: asusrouter.com or 192.168.1.1
- Linksys: 192.168.1.1
- D-Link: 192.168.0.1
Navigate to your WAN or Internet settings. Look for DNS Server fields under the WAN configuration (not the LAN/DHCP section). If they are set to automatic (ISP-assigned) and you suspect the ISP DNS is at fault, override them manually with 1.1.1.1 and 8.8.8.8. Save and reboot the router. Clients that renew their DHCP lease will pick up the new DNS servers automatically; you can force a renewal with ipconfig /release followed by ipconfig /renew on Windows.
Step 5: Inspect Your Hosts File
The hosts file is checked before any DNS query is made. If someone — malware, a misconfigured app, or a developer tool — added an entry pointing your domain to 0.0.0.0 or an incorrect IP, you will get a connection failure that mimics NXDOMAIN.
Windows
Open Notepad as Administrator, then open the path above. Look for any lines containing the domain that is failing. Lines starting with # are comments and are harmless. Any active line with the target domain should be removed or commented out unless you deliberately put it there.
macOS and Linux
Scroll through the file and remove any suspicious entries. Save with Ctrl+O, exit with Ctrl+X.
Step 6: Disable VPN, Proxy, or Security Software Temporarily
VPN clients route DNS queries through their own servers, and if the VPN tunnel is half-open or the VPN's DNS is misconfigured, all lookups fail with NXDOMAIN. Security suites like some antivirus products also intercept DNS to filter malicious domains — if their filter database is corrupt or their internal resolver crashes, legitimate domains get blocked.
Disconnect your VPN completely (not just pause it) and test the site again. If it loads, the problem is with the VPN's DNS leak protection settings or its DNS server. Most VPN clients have a setting under Advanced or Connection to specify a custom DNS — set it to 1.1.1.1. If you use a proxy configured in Windows settings, go to Settings > Network and Internet > Proxy and toggle off Use a proxy server.
Step 7: Renew Your IP and Reset the Network Stack
On Windows, a deeper network stack reset can clear issues that a simple cache flush misses. Run the following commands in an Administrator Command Prompt in sequence:
Restart the computer after running all five commands. The netsh int ip reset and netsh winsock reset commands rewrite core TCP/IP registry keys and the Winsock catalog respectively — this fixes corruption caused by malware or aggressive network-modifying software.
Step 8: Check for DNS Hijacking or Malware
Some malware specifically targets DNS settings to redirect users to phishing pages. A side effect is that legitimate domains sometimes return NXDOMAIN if the malicious DNS server does not have a record for them. Signs include: multiple unrelated sites failing, new browser toolbars you did not install, or slow browsing with occasional ad redirects.
Run a scan with Malwarebytes Free (malwarebytes.com) which specifically targets DNS hijackers. After cleaning, revisit your network adapter DNS settings and your router DNS settings to make sure they were not altered.
How to Verify the Fix Worked
After applying any fix, do not just reload the tab — Chrome may pull from its own cache. Open a new Incognito window (Ctrl+Shift+N) and navigate to the site fresh. To confirm DNS is resolving correctly from the command line:
This queries Cloudflare's resolver directly for the domain. If you get a valid A record back, DNS is working. If you still get NXDOMAIN or Non-existent domain from an external resolver, the issue is with the domain itself — not your machine.
When the Problem Is on the Domain Owner Side
If external tools confirm the domain returns NXDOMAIN everywhere, the fix is not on your computer — it is with the domain's DNS configuration. Common causes include:
- Expired domain registration: Renew at the registrar and allow 1–4 hours for the NS records to propagate back into the root zone.
- Nameservers removed or misconfigured: Check that the domain's nameservers at the registrar match the nameservers at your DNS host. A mismatch after a host migration will cause NXDOMAIN globally.
- DNS host account suspended: If the DNS hosting account was suspended for non-payment, all zones hosted there go dark. Contact your DNS provider.
- Missing A or CNAME record: The domain exists but has no record pointing to a server. Log into your DNS management panel and add the missing record.
Preventing NXDOMAIN Errors in the Future
For home users, the single most impactful change is switching to a reliable public DNS server (Cloudflare or Google) on both the router and individual machines. ISP DNS is often the first thing to fail during network incidents.
For domain owners, set calendar reminders for domain renewal at least 30 days before expiry and enable auto-renew at the registrar. Monitor your authoritative DNS records with an uptime tool — many DNS monitoring services will alert you within minutes if your zone stops resolving. Keep registrar and DNS hosting login credentials current and use two-factor authentication to prevent unauthorized changes that could wipe your DNS records.
For developers and IT admins, avoid hardcoding DNS entries in hosts files across machines — they are easy to forget and create exactly the kind of stale-record problem that produces NXDOMAIN six months later when infrastructure changes.
Quick Reference: Most Common Fixes by Symptom
- Only one site fails, others work fine: Flush OS and Chrome DNS cache. Check hosts file for a rogue entry.
- Multiple sites fail on one machine: Change DNS servers on the adapter. Reset Winsock. Check for malware.
- All devices on your network fail: Fix DNS settings in the router. Reboot the router and modem.
- Site fails everywhere (confirmed with external tool): Problem is with the domain's DNS — check registration expiry, nameserver configuration, and DNS records.
- Fails only when VPN is active: Reconfigure VPN DNS settings or contact VPN provider support.
DNS_PROBE_FINISHED_NXDOMAIN looks alarming but it is one of the more solvable browser errors once you understand what layer the fault sits on. Work through the steps above methodically, verify after each one, and you will have the answer in a matter of minutes.