Fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome

Encountering DNS_PROBE_FINISHED_NXDOMAIN when attempting to open a website in Google Chrome, Brave, or Microsoft Edge can bring your productivity or streaming to a standstill.

The abbreviation NXDOMAIN stands for Non-Existent Domain. In technical terms, the DNS lookup chain attempted to translate the human-readable domain into a machine-routable IPv4/IPv6 address, but received a definitive response indicating the domain record could not be resolved.

When this error happens across all devices for a specific domain, the domain registration may have lapsed or nameservers are misconfigured. If your domain is proxied by Cloudflare, check our troubleshooting guide for Cloudflare Error 522 Connection Timed Out.

However, when the domain loads on cellular data or other machines, the root cause is stale local OS cache, corrupted socket pools, or malfunctioning ISP DNS resolvers. To compare latency and reliability across top recursive resolvers, review our best DNS settings benchmarks for streaming.

This guide walks you through fixing this error on Windows, macOS, and inside Google Chrome.

---

Technical Diagnostic Flowchart

[Browser Address Bar: domain.com]
              │
              ▼
   [Chrome Internal Host Cache] ──(Hit?)──► Connect to IP
              │ (Miss)
              ▼
    [Operating System DNS Cache] ──(Hit?)──► Connect to IP
              │ (Miss)
              ▼
       [Router / ISP DNS] ─────────(Hit?)──► Connect to IP
              │ (Error Response: RCODE 3 / NXDOMAIN)
              ▼
[Google Chrome Displays: DNS_PROBE_FINISHED_NXDOMAIN]

On smart TVs and streaming sticks, similar DNS lookup drops cause apps to throw errors like Firestick Connected with Problems or IPTV playlist synchronization failures.

---

Step 1: Flush Chrome's Internal Host Cache and Socket Pools

Google Chrome maintains its own internal DNS cache layer separate from the underlying operating system. If Chrome cached an initial NXDOMAIN response during transient network downtime, it will continue rejecting requests for up to several hours.

Instructions:

1. Open a new tab in Chrome.
2. Enter the following URL into the omnibox:

   chrome://net-internals/#dns
   

3. Click the Clear host cache button.
4. Next, navigate to:

   chrome://net-internals/#sockets
   

5. Click Close idle sockets, then click Flush socket pools.
6. Close and relaunch Google Chrome.

---

Step 2: Flush the OS DNS Cache and Reset Winsock (Windows)

On Windows 10 and 11, corrupt entries in the DNS Client Service (dnscache) can poison all system-wide lookups.

Open PowerShell or Command Prompt as Administrator:

# 1. Flush local DNS resolver cache
ipconfig /flushdns

# 2. Release current DHCP IP assignment
ipconfig /release

# 3. Renew fresh DHCP IP and DNS parameters from router
ipconfig /renew

# 4. Reset low-level TCP/IP Winsock catalog
netsh winsock reset

# 5. Reset IP stack configuration
netsh int ip reset

Restart your computer after executing these commands to allow the network stack to reinitialize clean socket bindings.

---

Step 3: Flush DNS Cache on macOS

On Apple macOS (Sonoma, Ventura, Monterey), the mDNSResponder daemon manages unicast and multicast DNS resolution.

Open Terminal on Mac and run:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Type your administrator password when prompted. The command will run silently and immediately clear all cached DNS records.

---

Step 4: Switch to Reliable Public DNS Resolvers

If your ISP's recursive resolvers are experiencing downtime or propagation delays, your device will consistently receive NXDOMAIN responses. Switching to Tier-1 Anycast resolvers solves this instantly.

Recommended Resolver Addresses:

• Cloudflare: 1.1.1.1 and 1.0.0.1
• Google Public DNS: 8.8.8.8 and 8.8.4.4

Quick Windows Setup via PowerShell:

# Set primary interface to Cloudflare and Google DNS
Get-NetAdapter | Where-Object Status -eq "Up" | Set-DnsClientServerAddress -ServerAddresses ("1.1.1.1", "8.8.8.8")

---

Step 5: Audit the Local Hosts File for Stray Overrides

Malicious software, ad-blocking tools, or past local development setups often write hardcoded loopback redirects (127.0.0.1 or 0.0.0.0) to your operating system's hosts file.

Inspecting the Hosts File:

• Windows Location: C:\Windows\System32\drivers\etc\hosts
• macOS / Linux Location: /etc/hosts

Ensure that no production domain names you are trying to visit are mapped to local loopback addresses. If present, delete the line and save the file with administrator privileges.

---

Step 6: Disable VPN Network Adapters & Proxy Filtering

Virtual Private Networks (VPNs) like NordVPN, ExpressVPN, or WireGuard create virtual TAP/TUN network interfaces. When these adapters fail to unbind properly upon disconnection, they leave system routing tables pointing to defunct DNS proxies:

# Windows Command to check active DNS servers per interface:
Get-DnsClientServerAddress

If you observe an adapter labeled TAP-Windows Adapter V9 or WireGuard Tunnel asserting priority over your Wi-Fi interface, disable the adapter in Control Panel > Network Connections or reinstall your VPN client software.

---

Technical Summary Checklist

Action Item	Method	Verified
Clear browser socket cache	Chrome net-internals flush	[x]
Flush OS resolver cache	ipconfig /flushdns (Win) / dscacheutil (Mac)	[x]
Reset Winsock catalog	netsh winsock reset	[x]
Switch upstream DNS	Set adapter to 1.1.1.1 and 8.8.8.8	[x]
Hosts file inspection	Remove invalid 127.0.0.1 loopbacks	[x]

Following these diagnostic procedures guarantees that corrupt local state is eliminated. For additional network optimization blueprints, explore our Network & DNS knowledgebase, read our editorial policy, or submit diagnostic feedback via our contact form.