Web Browsers

How to Fix DNS_PROBE_FINISHED_NXDOMAIN

This DNS error means your browser couldn't find the address for the website. It's almost always fixable on your end in a few steps.

Priya Sharma Updated Jun 30, 2026 · 2 min read
How to Fix DNS_PROBE_FINISHED_NXDOMAIN
Photo: Mikey Harris · Unsplash
On this page
  1. First: double-check the URL
  2. Flush your DNS cache
  3. Change your DNS server
  4. Restart your router
  5. Check your VPN
  6. When the site genuinely doesn't exist

DNS_PROBE_FINISHED_NXDOMAIN is Chrome's way of saying it couldn't translate the website's name into an IP address — the DNS lookup returned "no such domain" (NXDOMAIN). Before panicking, note that this is one of the most common and fixable browser errors.

First: double-check the URL

A simple typo is the most common cause. Make sure you've spelled the domain correctly and haven't accidentally added an extra character.

Flush your DNS cache

Your computer stores DNS results locally. If a cached result is wrong or stale, you'll keep getting this error even after the problem is resolved elsewhere.

Windows: open Command Prompt as administrator and run:

ipconfig /flushdns

Mac: open Terminal and run:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Try loading the site again after flushing.

Change your DNS server

If your ISP's DNS server is struggling, switching to a public one often resolves NXDOMAIN errors immediately.

  1. On Windows: open Control Panel > Network and Sharing Center > Change adapter settings.
  2. Right-click your active connection and choose Properties.
  3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  4. Choose Use the following DNS server addresses and enter 8.8.8.8 and 8.8.4.4.

On Mac: go to System Settings > Network, select your connection, click Details, go to the DNS tab, and add 8.8.8.8.

Restart your router

Your router also caches DNS results. A full power cycle (unplug 30 seconds, plug back in) clears the router's cache.

Check your VPN

If you use a VPN, try disconnecting it and loading the site. VPNs route DNS queries differently and sometimes cause NXDOMAIN errors for sites that are perfectly accessible without them.

When the site genuinely doesn't exist

Sometimes NXDOMAIN means exactly what it says — the domain has expired, been deleted, or was mistyped. Search for the site rather than typing the URL directly, or try a cached version via Google's cache.

Need more help? Ask us.

Frequently asked questions

Why does this error appear for some sites but not others?

If certain sites trigger NXDOMAIN while others load fine, your DNS server is likely resolving most domains correctly but has a stale or missing record for those specific ones. Changing to Google or Cloudflare DNS (as described above) almost always resolves this, since those servers have very comprehensive and up-to-date records.

I flushed my DNS and changed DNS servers, but the error persists. What next?

Try using a different browser to confirm it's not browser-specific. Then try a different device on the same network. If other devices work fine, the issue is with your computer's network stack — resetting Winsock (netsh winsock reset in an administrator Command Prompt) is the next step on Windows.

Priya Sharma

Hands-on help writer who tests phone, tablet and security fixes on real devices before recommending them.

Comments & Questions (0)

No comments yet — be the first to ask. Comments appear after review.

Leave a comment

Your comment appears after our team approves it. Or sign in to post faster.

Keep reading