Fixing DNS_PROBE_FINISHED_NXDOMAIN Error

DNS_PROBE_FINISHED_NXDOMAIN indicates that the resolver your browser queried couldn’t locate the domain you entered, resulting in a Name Error. To resolve this, you can try one of three solutions: flush your computer’s DNS cache, switch to a public DNS resolver like 1.1.1.1 or 8.8.8.8, or correct any typos in the URL. This guide provides a step-by-step troubleshooting process, from least to most invasive, with specific commands for Windows, macOS, and Linux, as well as diagnostic checks to determine if the issue is on your device or with the domain itself.

What DNS_PROBE_FINISHED_NXDOMAIN Means

NXDOMAIN is response code 3 in the DNS protocol, defined as Name Error in RFC 8020. The resolver checked the DNS hierarchy and confirmed the domain doesn’t exist. Chromium-based browsers label this as DNS_PROBE_FINISHED_NXDOMAIN, indicating that the probe completed before failing. You’ll see this in Google Chrome, Microsoft Edge, Brave, Opera, and Vivaldi. Firefox uses a different error message, so seeing NXDOMAIN indicates a Chromium-based browser.

This error narrows down the troubleshooting scope. The browser reached a resolver, which responded that the domain isn’t in DNS. The issue could be local (stale cache or incorrect hosts file), upstream (ISP resolver returning incorrect data or filtering the domain), or authoritative (no records, expired domain, or DNS misconfiguration by the domain owner).

Common Causes Before You Touch Anything

The fix depends on where the issue lies. The table below pairs each likely cause with its targeted fix, allowing you to skip to the relevant solution if symptoms point to a specific issue.

Cause	Location	Fix
Typo or extra character in the URL	Address bar	Re-check spelling
Stale OS DNS cache	Operating system	Flush DNS
Stale browser DNS cache	Chrome, Edge, Brave, etc.	Flush cache at chrome://net-internals/#dns
ISP resolver returning bad data	Network upstream	Switch to a public resolver
Hosts file mapping pointing nowhere	OS file system	Edit hosts file
VPN or antivirus DNS interference	Third-party software	Disable temporarily
Router holding stale DNS state	Router	Power-cycle the router
Domain expired or misconfigured	Domain owner	Verify with dig or WHOIS

If you’re unsure which row applies, follow the methods below from top to bottom. Each is non-destructive and takes under a minute.

Method 1: Verify the URL and Test a Second Browser

Type the address fresh instead of using a stored autocomplete entry. A single transposed letter or stray character can cause NXDOMAIN responses, and the browser will keep auto-completing the wrong string until you overwrite it. Look for similar-looking characters: a Cyrillic letter from chat, a hyphen instead of an underscore, or a double dot in the hostname will all cause NXDOMAIN.

If the URL is correct, try opening it in a second browser. If Firefox loads the page while Chrome shows NXDOMAIN, it’s likely a Chrome-side cache issue rather than a network or domain problem. Testing the URL on a phone using cellular data instead of Wi-Fi is another quick isolation step. If the page loads on the phone but not on the laptop, the issue is with the laptop or home network, not the domain.

Method 2: Flush Chrome’s Internal DNS Cache

Chromium browsers maintain a separate DNS cache from the operating system resolver cache. Flushing one doesn’t affect the other, so this step is worth trying even after a system-level flush.

Paste this into the address bar and press Enter:

chrome://net-internals/#dns