How to Fix DNS_PROBE_FINISHED_NXDOMAIN

What Is DNS_PROBE_FINISHED_NXDOMAIN?

DNS_PROBE_FINISHED_NXDOMAIN is a Chrome-family browser error that appears when a DNS lookup failed — meaning your browser sent a request to a DNS server asking "what is the IP address for this domain?" and the server replied that the domain does not exist (NXDOMAIN = Non-Existent Domain).

The Domain Name System (DNS) works like the internet's address book. When you type example.com, your device queries a DNS resolver to translate that human-readable name into a numeric IP address like 93.184.216.34. If that translation — the dns resolution failed — the browser has nowhere to connect to and shows this error.

You may see this error displayed in slightly different ways depending on your browser and operating system:

Root Causes

Before jumping to fixes, it helps to understand why a dns probe finished nxdomain error occurs. The cause determines the fastest path to resolution.

Quick Fixes to Try First

These three steps resolve the majority of how to fix dns probe finished nxdomain cases in under two minutes. Try them before diving into OS-specific steps.

Windows Fixes

All commands below require Command Prompt or PowerShell run as Administrator.

1. Flush the DNS cache

This is the most effective first step for a dns lookup failed error on Windows. It clears all cached DNS records and forces fresh lookups.

ipconfig /flushdns

You should see: "Successfully flushed the DNS Resolver Cache."

2. Release and renew IP address

ipconfig /release
ipconfig /renew

3. Reset Winsock and TCP/IP stack

Winsock corruption can cause persistent dns resolution failed errors even after flushing the cache.

netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /registerdns

4. Change DNS server to Google or Cloudflare

Go to Settings → Network & Internet → Change adapter options → right-click your connection → Properties → select Internet Protocol Version 4 (TCP/IPv4) → Properties → enter:

5. Check and clean the hosts file

Open Notepad as Administrator and open C:\Windows\System32\drivers\etc\hosts. Remove any lines that reference the domain you're trying to reach.

6. Clear Chrome's internal DNS cache

Chrome maintains its own DNS cache separate from Windows. Navigate to:

chrome://net-internals/#dns

Click Clear host cache, then also visit chrome://net-internals/#sockets and click Flush socket pools.

macOS Fixes

1. Flush DNS cache

Open Terminal and run the appropriate command for your macOS version:

# macOS Ventura, Sonoma, Sequoia (13+)
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# macOS Monterey (12)
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# macOS Big Sur (11)
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

2. Renew DHCP lease

Go to System Settings → Network → select your active connection → click Details → TCP/IP tab → Renew DHCP Lease.

3. Change DNS server

In the same Details → DNS tab, click the + button and add 8.8.8.8 and 1.1.1.1. Remove any existing entries that look incorrect.

4. Check the hosts file

sudo nano /etc/hosts

Remove any lines referencing the affected domain. Press Ctrl+X → Y → Enter to save.

Linux Fixes

DNS cache management on Linux depends on which resolver service your distribution uses. A dns lookup failed error typically manifests in the terminal as "Name or service not known".

1. Flush DNS cache

# systemd-resolved (Ubuntu 18.04+, Fedora, Arch)
sudo systemd-resolve --flush-caches
# Verify: sudo systemd-resolve --statistics | grep "Cache"

# nscd (older distros)
sudo systemctl restart nscd

# dnsmasq
sudo systemctl restart dnsmasq

2. Change DNS server

# Edit resolved.conf
sudo nano /etc/systemd/resolved.conf

# Add or update:
[Resolve]
DNS=8.8.8.8 1.1.1.1
FallbackDNS=8.8.4.4 1.0.0.1

# Restart the service
sudo systemctl restart systemd-resolved

3. Test DNS resolution directly

# Test with a specific DNS server
dig @8.8.8.8 example.com

# Or using nslookup
nslookup example.com 8.8.8.8

Mobile Fixes (iOS & Android)

Advanced Fixes for Persistent Issues

Disable VPN or proxy

VPNs route DNS queries through their own resolvers. If the VPN's DNS server is misconfigured or the VPN is blocking the domain, you'll see a dns probe finished nxdomain error. Temporarily disable the VPN and test. If the site loads, contact your VPN provider or configure it to use a custom DNS.

Disable antivirus DNS filtering

Products like Avast, Kaspersky, and Norton intercept DNS queries for their "web shield" features. Temporarily disabling the web shield (not the full antivirus) can confirm if it's the cause. If it is, add the domain to the antivirus whitelist rather than leaving the shield off permanently.

Check if the domain has expired

If you own the domain, log into your registrar and verify the expiry date. An expired domain returns a genuine NXDOMAIN response — no amount of cache flushing will fix it until the domain is renewed.

# Check domain registration status
whois example.com | grep -i "expir"

# Or use dig to query authoritative nameservers
dig +trace example.com

Verify DNS propagation

If you recently updated DNS records, propagation can take up to 48 hours. Use a tool like dnschecker.org to see which regions have received the new records. In the meantime, you can manually override DNS on your device by adding the correct IP to your hosts file.

Reset Chrome flags

Experimental Chrome flags can interfere with DNS resolution. Navigate to chrome://flags and click Reset all, then restart the browser.

Prevention & Monitoring

Most dns resolution failed errors are reactive — you only find out when a user reports it. The better approach is proactive monitoring so you know before your users do.

Frequently Asked Questions