How to Fix DNS_PROBE_FINISHED_NXDOMAIN (Chrome, Edge, Brave) آموزش رفع خطای DNS_PROBE_FINISHED_NXDOMAIN در کروم، اج و بریو

You try to visit a website and Chrome shows: "This site can't be reached. [website] 's server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN."

This error means your browser asked the DNS server to look up the website's IP address, and the DNS server said "that domain doesn't exist" (NXDOMAIN = Non-Existent Domain). But the website might be perfectly fine — the problem is usually on your end.

Here are the fixes, in order of most likely to work.

Fix 1: Check the URL

Seriously — the most common cause is a typo. Double-check:

• Spelling (gogle.com vs google.com)
• TLD (.com vs .net vs .dev)
• No extra characters or spaces

If the URL looks correct, continue.

Fix 2: Flush Your DNS Cache

Your computer caches DNS lookups. If the cache has a stale or corrupted entry, you get this error.

Windows:

ipconfig /flushdns

Mac:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux:

sudo systemd-resolve --flush-caches

Chrome's internal DNS cache:

1. Type chrome://net-internals/#dns in the address bar
2. Click Clear host cache

Fix 3: Change Your DNS Server

Your ISP's DNS servers might be slow or down. Switch to a public DNS:

Windows:

1. Settings → Network & Internet → Change adapter options
2. Right-click your connection → Properties
3. Select "Internet Protocol Version 4" → Properties
4. Select "Use the following DNS server addresses"
5. Enter: 1.1.1.1 and 1.0.0.1 (Cloudflare) or 8.8.8.8 and 8.8.4.4 (Google)
6. Click OK

Mac:

1. System Settings → Network → WiFi → Details → DNS
2. Remove existing entries
3. Add 1.1.1.1 and 1.0.0.1

iPhone: Settings → WiFi → tap (i) next to your network → Configure DNS → Manual → add 1.1.1.1

Android: Settings → Network → Private DNS → Enter one.one.one.one

Check your DNS configuration with our DNS Toolbox.

Fix 4: Release and Renew IP

Your network configuration might be stale.

Windows:

ipconfig /release
ipconfig /renew

Mac/Linux: Turn WiFi off and back on, or:

sudo ifconfig en0 down && sudo ifconfig en0 up

Fix 5: Disable VPN or Proxy

VPNs and proxies can interfere with DNS resolution. Temporarily disable them and try again.

If it works without the VPN, your VPN's DNS is the problem. Check our VPN Leak Test to see which DNS servers your VPN is using.

Fix 6: Clear Browser Cache and Cookies

1. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac)
2. Select "All time"
3. Check "Cached images and files" and "Cookies"
4. Click Delete

Fix 7: Reset Chrome Flags

Experimental Chrome flags can cause DNS issues:

1. Type chrome://flags in the address bar
2. Click Reset all at the top
3. Restart Chrome

Fix 8: Disable Antivirus/Firewall Temporarily

Security software sometimes blocks DNS queries. Temporarily disable your antivirus and try again. If it works, add an exception for your browser.

Fix 9: Check the hosts File

Your computer has a hosts file that can override DNS. If someone (or malware) added an entry, it can cause NXDOMAIN.

Windows: Open C:\Windows\System32\drivers\etc\hosts in Notepad (as admin) Mac/Linux: Open /etc/hosts

Look for the domain you are trying to visit. If it is listed with the wrong IP (like 0.0.0.0 or 127.0.0.1), remove that line.

Fix 10: The Domain Might Actually Not Exist

If none of the above works, the domain genuinely might not exist:

• It expired (check with our WHOIS Lookup)
• It was never registered
• It was taken down

Look up the domain with our WHOIS Lookup to check its registration status, or use our DNS Toolbox to see if it has any DNS records at all.

What Causes This Error?

Related Tools

• DNS Toolbox — look up DNS records for any domain
• WHOIS Lookup — check if a domain is registered
• VPN Leak Test — check if your VPN is causing DNS issues
• What's My IP — verify your connection is working