Fix DNS_PROBE_FINISHED_NXDOMAIN (2026)
Fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome and Edge: flush DNS, check the hosts file, reset DNS servers and clear the browser cache. Step-by-step solutions.
Locahl Team
Table of Contents
DNS_PROBE_FINISHED_NXDOMAIN means the browser could not resolve the domain to an IP address. The DNS lookup returned "no such domain" (NXDOMAIN). The usual causes are a stale DNS cache, a wrong or leftover entry in your hosts file, a failing DNS server, or simply a typo in the URL. In most cases, flushing DNS and checking the hosts file fixes it in under a minute.
Fix DNS_PROBE_FINISHED_NXDOMAIN
Work through these steps in order; stop when the page loads:
1. Check the URL for typos and try the bare domain in a new tab. 2. Flush the DNS cache for your OS — see flush DNS on Windows, flush DNS on Mac, or flush DNS on Linux. 3. Clear the browser host cache at chrome://net-internals/#dns (or edge://net-internals/#dns), then Clear host cache and Flush socket pools. 4. Inspect the hosts file for a wrong or leftover line mapping that domain to an unreachable IP. 5. Switch DNS servers to Cloudflare 1.1.1.1 or Google 8.8.8.8 and retry. 6. Restart networking (toggle Wi-Fi, or reboot the router for ISP-level DNS issues).
When the hosts file is the cause
If only one custom domain (like myapp.test) shows NXDOMAIN, the hosts file is the prime suspect. Open it and confirm the line is valid:
127.0.0.1 myapp.testA line pointing to a wrong IP, a commented-out entry, or a malformed line (with http:// or a port) will cause resolution to fail. See the hosts file syntax guide and, on Mac, hosts file not working.
Verify the fix
nslookup myapp.testIf the command line resolves correctly but the browser still shows NXDOMAIN, the browser cache is stale — repeat step 3.
Prevent it from recurring
Leftover testing entries are a frequent cause. A hosts manager like Locahl lets you toggle entries off instead of deleting them and flushes DNS automatically, so old mappings never linger to trigger NXDOMAIN later.
_Last tested: June 2026 in Chrome 137 and Edge on Windows, macOS and Linux._
Ready to simplify your workflow?
Stop wasting time with the terminal. Locahl lets you manage your hosts file in a few clicks, with automatic validation and no risk of errors.
- Intuitive visual interface
- Automatic DNS flush
- Multi-environment management
- Automatic backups
- JSON Import/Export
Reader Reviews
"It was a stale hosts entry. Flushing DNS as the guide says fixed NXDOMAIN immediately."
June 12, 2026
"Switching to 1.1.1.1 and clearing Chrome host cache solved it. Clear, ordered steps."
June 10, 2026
"Worked for me. A router-reboot note would help less technical readers."
June 8, 2026
Frequently Asked Questions
What does DNS_PROBE_FINISHED_NXDOMAIN mean?
NXDOMAIN means the domain name could not be resolved to an IP address — the DNS lookup returned "no such domain". It can be a typo, a DNS server issue, a stale cache, or a wrong hosts file entry.
How do I fix DNS_PROBE_FINISHED_NXDOMAIN fast?
Flush the DNS cache, clear the browser host cache, and check the hosts file for a wrong or leftover entry. Then try a public resolver like 1.1.1.1.
Why does only one site show NXDOMAIN?
That domain likely has a bad hosts file line or a DNS record problem, while other sites resolve normally.
Can the hosts file cause NXDOMAIN?
Yes. A custom domain mapped to an unreachable IP, or a leftover entry from old testing, can make a site fail to resolve.
Related Articles
Clear Chrome DNS Cache on Mac Fast
Clear Chrome DNS cache on Mac with chrome://net-internals, flush macOS DNS, restart sockets and fix stale local domains after hosts changes.
Locahl Team
Developer tools team
127.0.0.1 vs localhost: What’s the Difference?
127.0.0.1 vs localhost explained: both point to your machine, but they differ in DNS resolution, IPv6, and hosts file behavior. When to use each, with examples.
Locahl Team
Developer tools team
Clear DNS Cache in Microsoft Edge (2026)
Clear the DNS cache in Microsoft Edge with edge://net-internals/#dns, flush socket pools, and clear the Windows DNS cache so hosts changes take effect.
Locahl Team
Developer tools team
Which TLD to Use for Local Development (.test vs .localhost)
Which TLD to use for local development: prefer .test, avoid .dev and .local. Why .test is reserved, how to map it in the hosts file, and HTTPS tips.
Locahl Team
Developer tools team
What Is localhost? A Clear Explanation
What is localhost? It is the hostname for your own computer, resolving to 127.0.0.1 (or ::1) via the hosts file. How it works, why it matters, and common issues.
Locahl Team
Developer tools team