How to Fix DNS_PROBE_FINISHED_NXDOMAIN

The DNS_PROBE_FINISHED_NXDOMAIN error is one of the most common browser errors. It means the DNS lookup for a domain returned NXDOMAIN — the domain doesn't exist in DNS. Here's how to diagnose and fix it.

What Does NXDOMAIN Mean?

NXDOMAIN stands for Non-Existent Domain. When a DNS resolver returns this response, it's saying: "I checked, and this domain name has no DNS records." Your browser translates this into the DNS_PROBE_FINISHED_NXDOMAIN error page.

Common Causes

• Typo in the URL — The simplest and most common cause.
• Domain has expired — The registrar removed DNS delegation.
• DNS records not configured — The domain exists but has no records.
• Nameservers misconfigured — Pointing to wrong or non-existent nameservers.
• Local DNS cache issue — Stale cached records on your computer.
• ISP DNS problems — Your ISP's DNS resolver is having issues.
• VPN or proxy interference — Network configuration blocking DNS.

Fixes for Website Visitors

If you're seeing this error when visiting someone else's website:

1. Check the URL

Double-check for typos. A single wrong character causes NXDOMAIN.

2. Flush Your DNS Cache

# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Windows
ipconfig /flushdns

# Chrome browser cache
chrome://net-internals/#dns → Clear host cache

3. Try a Different DNS Resolver

Change your DNS settings to use Google (8.8.8.8) or Cloudflare (1.1.1.1) instead of your ISP's resolver.

4. Disable VPN/Proxy

Temporarily disable any VPN or proxy to rule out network interference.

5. Clear Browser Cache

Try incognito/private mode or clear your browser's cache and cookies.

6. Restart Your Router

Your router may have a stale DNS cache. Power cycle it to clear.

Fixes for Domain Owners

If your own domain is showing NXDOMAIN:

1. Verify Domain Registration

Check that your domain hasn't expired. Log in to your registrar and verify the expiration date. Enable auto-renewal to prevent this.

2. Check Nameserver Configuration

Use our Nameserver Lookup Tool or run:

dig NS yourdomain.com

Verify the nameservers returned are correct and active.

3. Verify DNS Records Exist

dig A yourdomain.com @your-nameserver

Query your authoritative nameserver directly. If it returns NXDOMAIN, your records are missing.

4. Check for Registrar Hold

Some registrars place domains on hold for verification or policy violations. Check your registrar account for any notices.

5. Wait for Propagation

If you recently changed nameservers, the new configuration may not have propagated yet. Wait up to 48 hours.

Diagnosing with Command Line

Use these commands to pinpoint the issue:

# Check if the domain resolves at all
dig yourdomain.com ANY

# Query specific nameservers
dig @8.8.8.8 yourdomain.com A
dig @1.1.1.1 yourdomain.com A

# Check nameserver delegation
dig NS yourdomain.com @a.gtld-servers.net

If the domain resolves on some resolvers but not others, it's likely a propagation or caching issue. If it fails everywhere, the problem is at the registrar or DNS provider level.