DNS_PROBE_FINISHED_NXDOMAIN means your browser asked a DNS server for a website’s IP address and was told the domain does not exist (NXDOMAIN). Typical causes are a typo, an expired or unregistered domain, wrong DNS records, or stale local DNS data. It appears in Chrome, Edge, Brave and other Chromium browsers.
Quick fix in 3 steps:
- Check the address for typos, then reload in an Incognito window.
- Flush your DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS).
- Switch your DNS server to 1.1.1.1 or 8.8.8.8 and turn off any VPN or proxy. Own the domain? Jump to the site-owner checks.
Jump to: For visitors | For site owners
This guide explains what the dns_probe_finished_nxdomain error means, how to fix it on Windows, Mac, Android and Chrome, and what site owners should check when their own domain triggers it. It also covers localhost, Django and .test domains, and how to prevent NXDOMAIN errors. For DNS basics see our DNS guide; for lookups see the nslookup guide.
What does dns_probe_finished_nxdomain mean?
DNS_PROBE_FINISHED_NXDOMAIN means your browser sent a DNS lookup for a domain and got back a definitive “this domain does not exist” response (NXDOMAIN). It shows up in Chrome, Edge, and other Chromium browsers when the requested hostname has no matching DNS record anywhere your resolver can find — because the domain isn’t registered, its DNS records were deleted or misconfigured, or a typo sent the request to a name that was never created.
Why Does It Happen?
The browser tried to look up the IP address for a domain, the DNS probe finished, and the answer was NXDOMAIN, short for Non-Existent Domain. Here is the breakdown:
- DNS: The distributed database that maps domain names (like example.com) to IP addresses.
- Probe: The action of querying the DNS to locate the server’s IP.
- Finished: The process completed.
- NXDOMAIN: The domain doesn’t exist (or can’t be resolved).
When you combine those concepts, it means your browser tried to find a site and the DNS responded, “We have no idea where that is.”
Possible Causes of DNS_PROBE_FINISHED_NXDOMAIN
There can be a broad array of issues triggering the dns_probe_finished_nxdomain cause. Let’s outline the most common:
Typo or Wrong URL
The simplest cause: a misspelled domain, a wrong extension (.con instead of .com) or a link to a domain that was never registered. A web server being down does not cause NXDOMAIN; DNS is resolved before the server is contacted, so an offline server shows a different error such as a timeout or connection refused.
DNS Misconfiguration or Propagation
Sometimes the underlying reason is a misconfigured DNS record or a recent DNS change that hasn’t yet propagated worldwide. If your name servers or A records haven’t updated across the internet, you might see an nxdomain dns error. This typically happens shortly after transferring a domain or changing hosting providers.
Expired Domain
Another potential scenario is that the domain name has expired. If an owner forgets to renew their domain, the DNS records effectively vanish, and all visitors will see an NXDOMAIN response. If you’re the domain owner, verifying your registration status should be high on your to-do list.
Firewall Access Block
Occasionally, overzealous firewall or antivirus software can block legitimate requests. If a firewall intercepts a DNS query and deems it unsafe, the process never completes. This can cause your browser to interpret the domain as nonexistent, even though it’s functioning normally for everyone else.
ISP Issue
Your Internet Service Provider might experience DNS problems on their end, preventing you from reaching certain websites. If the ISP’s DNS servers are down or improperly configured, you’ll see nxdomain errors for domains that are otherwise accessible.
Cache Issues
Outdated DNS information stored locally in your browser, operating system, or router can cause the browser to fail in connecting to an updated server IP. As a result, you’ll receive a dns_probe_finished_nxdomain cause error message.
VPN, Proxy or Custom DNS Settings
A VPN, proxy or manually set DNS server sends your lookups to a resolver that may fail, filter the domain or hold stale records. If the site loads on mobile data but not on your Wi-Fi or VPN, this is the likely cause.
How to Fix dns_probe_finished_nxdomain
Work through these fixes in order. Visitors should start with the device fixes; if you own the domain, skip to the site-owner checks.
- For visitors: clear caches, change DNS, check VPN and firewall
- For site owners: check registration, nameservers, A records and propagation
For Visitors: Fix DNS_PROBE_FINISHED_NXDOMAIN on Windows, Mac, Android and Chrome
- Check the URL for typos and try Incognito mode.
- Flush the DNS cache (see Cache Clearance below).
- Switch to a public DNS server.
- Disable VPN, proxy and extensions, then retry.
- Test on mobile data to see whether the problem is your network or the domain.
Cache Clearance
One of the simplest yet most effective solutions is flushing your DNS cache, because old data can cause conflicts.
- On Windows: Open the Command Prompt (as administrator) and type:
ipconfig /flushdns
This command clears the local resolver cache, forcing your system to obtain fresh DNS information.
- On macOS: Launch Terminal and use the command:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Then enter your password if prompted. Once done, try reloading the page.
- Browser Cache (Chrome): Enter chrome://net-internals/#dns in your address bar, then click on the “Clear host cache” button. This ensures Chrome’s internal DNS cache is removed.
- Android: toggle airplane mode on and off, or forget and rejoin the Wi-Fi network. Then open Settings > Network & internet > Private DNS and set a public resolver hostname.
- Chrome Secure DNS: open Settings > Privacy and security > Security and turn Use secure DNS off, or pick a different provider, then reload.
- Linux (systemd-resolved): resolvectl flush-caches.
Local Hosts File
The hosts file on your system can override DNS queries. If an entry inside the hosts file points to the wrong IP or intentionally blocks a website, you’ll see an NXDOMAIN response. Removing or correcting incorrect entries can fix the dns_probe_finished_nxdomain cause right away.
For Site Owners: Check Your Domain, Nameservers and DNS Records
If visitors everywhere see the error, work through these checks:
- Registration: confirm the domain has not expired and is not in a grace or redemption period at your registrar.
- Nameservers: the NS records at the registrar must point to the DNS provider that actually holds your zone.
- Records: make sure an A record (IPv4) or AAAA record (IPv6) exists for the exact hostname, including www if you use it.
- Propagation: after DNS changes allow time for caches to expire; it depends on the TTL (see DNS propagation).
- Query a public resolver directly to see what the world sees.
nslookup example.com 1.1.1.1
dig +short NS example.com
dig +short A www.example.com
NXDOMAIN in the output means the name does not exist at that resolver. Hosting on a Contabo server? Manage zones as described in our DNS and rDNS management guide.
Switch to a New DNS Server
If your ISP’s DNS servers are unreliable, switching to a well-known public DNS can fix connectivity problems. Common options include Google Public DNS (8.8.8.8, 8.8.4.4) or Cloudflare DNS (1.1.1.1, 1.0.0.1). By changing your DNS servers to these, your machine will consult them for domain lookups instead of your ISP’s infrastructure.
On Windows 11: Settings > Network & internet > Wi-Fi (or Ethernet) > Hardware properties > DNS server assignment > Edit > Manual, then enter 1.1.1.1 and 8.8.8.8.
On macOS: System Settings > Network > Wi-Fi > Details > DNS > add 1.1.1.1 and 8.8.8.8. To confirm the domain really exists, run nslookup example.com 1.1.1.1;
if even the public resolver returns NXDOMAIN, the problem is the domain, not your device.
Request a New IP
Occasionally, your device’s IP configuration can create conflicts. Renewing your IP can solve issues that contribute to “dns_probe_finished_nxdomain fix” steps:
- Windows: Open Command Prompt and type:
ipconfig /release
ipconfig /renew
This forces your system to drop its current IP and request a new one.
macOS: Go to System Preferences → Network, pick your connection, then click Advanced → TCP/IP → Renew DHCP Lease.
Firewall, Antivirus, VPN and Proxy
Turn off your VPN or proxy and test again. If the page loads, change VPN server, set custom DNS inside the VPN app, or whitelist the domain. Re-enable your security software afterwards.
A misconfigured firewall can block DNS requests. Temporarily disable or adjust your firewall to see if the error disappears. If it does, fine-tune your firewall rules to white-list essential traffic. Always remember to reactivate your security measures once you verify the cause.
Internet Connectivity
Power cycle your router and modem if your internet is acting up. Simply unplug both devices for 30 seconds, then reconnect the modem first and the router second. This procedure flushes out any minor network hiccups, sometimes resolving the “dns_probe_finished_nxdomain” problem instantly.
Server Health
If you manage your own website, log in to your hosting dashboard and review your server’s resource usage or event logs. With a Contabo VPS, you can easily monitor key metrics like CPU, RAM, and disk space to ensure optimal performance. If your server is running but the issue persists, consider reaching out to our support team for further assistance.
Localhost, Django and .test Domains
On a development machine the error usually means the custom hostname was never mapped to an IP. Hostnames such as myapp.test or myapp.local do not exist in public DNS.
• Add a line to your hosts file: 127.0.0.1 myapp.test (Linux and macOS: /etc/hosts; Windows: C:\Windows\System32\drivers\etc\hosts, edit as administrator).
• Or run a local resolver such as dnsmasq to map a whole development domain.
• Django: add the hostname to ALLOWED_HOSTS in settings.py. A missing entry gives a 400 error, not NXDOMAIN; NXDOMAIN means the name does not resolve at all.
• Chrome resolves *.localhost to the loopback address, which makes it a handy dev domain.
Preventing NXDOMAIN Errors
Proactively managing your DNS environment will help avoid these frustrating nxdomain errors. Below are recommended measures:
Regular Audit of DNS Records
Scheduled reviews of DNS records ensure that old or invalid data isn’t hanging around. This includes verifying the correctness of your A, CNAME, and MX records, as well as any subdomain entries.
DNS Failover
DNS failover automatically redirects queries to a backup server if the primary one fails. By leveraging this approach, you can maintain near-constant availability for your domains—even if something goes wrong.
Anycast DNS Usage
Anycast DNS routes user requests to the geographically nearest server, improving latency and reliability. Using a robust Anycast network means fewer points of DNS failure, drastically reducing the risk of nxdomain errors.
Enable DNSSEC
DNS Security Extensions protect your DNS from tampering, like spoofing or cache poisoning. By digitally signing DNS data, DNSSEC ensures that a user receives valid DNS information, lowering the chance of misleading nxdomain responses.
TTL Values Policy
Time-to-Live (TTL) determines how long DNS information stays cached. Strategic TTL settings can accelerate DNS updates or, if set too high, delay the spread of corrections. Find the right balance based on how often your DNS changes.
Domain Renewals
Finally, keep an eye on your domain’s expiration date. Automate renewals whenever possible. An expired domain is the quickest route to producing an nxdomain dns error for all your visitors.
NXDOMAIN Attack – Detection and Prevention
While typical nxdomain errors stem from misconfigurations or DNS downtime, an nxdomain attack involves maliciously flooding an authoritative server with requests for non-existent domains. The goal is to overwhelm the server, preventing it from responding to legitimate queries. This scenario is known as a “nxdomain attack.”
How Does It Work?
Attackers often use botnets to send waves of DNS lookup requests for subdomains that aren’t registered. The server invests resources in trying to locate these fictitious subdomains, eventually overloading and timing out.
Detecting and Preventing nxdomain Attacks
- Anomaly Detection: Monitor your DNS traffic for sudden spikes in NXDOMAIN responses.
- Anycast DNS: Spread DNS resources across multiple locations, so traffic is routed to the nearest node, preventing any single node from getting swamped.
- Firewall and Rate Limiting: Apply rules that limit the number of requests from individual sources.
- Security Monitoring: Maintain logs of all DNS queries to quickly identify suspicious patterns.
By staying vigilant, you can shield your domain from a crippling nxdomain attack.
dns_probe_finished_nxdomain FAQ
Q: What does dns_probe_finished_nxdomain mean?
A: It indicates that the DNS lookup for a particular domain name found no associated IP address. In other words, the domain’s address can’t be resolved, so the browser reports an error.
Q: How do I fix dns_probe_finished_nxdomain?
A: Common fixes include flushing your DNS cache, verifying your local hosts file, checking domain health, switching to public DNS servers, and making sure no firewall is blocking the domain. If none of these work, the issue might be with the domain’s registration status or your ISP.
Q: Why am I seeing DNS_PROBE_FINISHED_NXDOMAIN on Android?
A: Android phones cache DNS at the OS level, separate from any app or browser. If a domain’s DNS record changed recently, your phone may still be holding the old (or missing) entry. Forget and rejoin your Wi-Fi network, or switch your connection’s DNS servers to a public resolver like 1.1.1.1 in Settings > Network > Advanced > Private DNS, then retry.
Q: How do I fix DNS_PROBE_FINISHED_NXDOMAIN on Mac?
A: On macOS, open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder to clear the local DNS cache, then reload the page. If that doesn’t help, check System Settings > Network > Wi-Fi > Details > DNS and try a public resolver instead of your ISP’s default.
Q: Why does this happen right after I buy a domain from GoDaddy?
A: A freshly registered domain needs time for its DNS records to propagate across the internet — this can take anywhere from a few minutes to 24–48 hours. If DNS_PROBE_FINISHED_NXDOMAIN appears immediately after registration, the domain likely hasn’t finished propagating yet rather than being misconfigured.
Q: Is DNS_PROBE_FINISHED_NXDOMAIN the same in Chrome and other browsers?
A: The DNS_PROBE_FINISHED_NXDOMAIN error string itself is Chromium-specific (Chrome, Edge, Brave, Opera). Firefox shows the same underlying problem as “Server Not Found,” and Safari shows “Safari Can’t Find the Server” — different wording, same root cause: no DNS record for that domain.
Q: Is DNS_PROBE_FINISHED_NXDOMAIN my fault or the website’s?
Test the same URL on mobile data or another network. If it loads there, the problem is on your device or network (cache, DNS server, VPN, hosts file). If it fails everywhere, the domain itself is the cause: a typo, an expired or unregistered domain, or missing DNS records. Only the site owner can fix that last case.
Q:How do I fix DNS_PROBE_FINISHED_NXDOMAIN on Mac or Android?
On Mac, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal, then reload. On Android, toggle airplane mode or forget and rejoin the Wi-Fi network, then set Private DNS to a public resolver such as one.one.one.one. In Chrome, also clear the host cache and retry in Incognito.
Q: Can a VPN cause DNS_PROBE_FINISHED_NXDOMAIN?
Yes. A VPN sends your DNS lookups to its own resolver, which may block a domain, fail to resolve it, or use stale records. Disconnect the VPN and reload the page. If the site now opens, switch VPN servers or enable the VPN’s DNS leak or custom DNS setting, or whitelist the domain.
Q: Why do I get DNS_PROBE_FINISHED_NXDOMAIN on localhost or a .test domain?
Custom development hostnames such as myapp.test or myapp.local only resolve if something maps them to an IP. Add a line like 127.0.0.1 myapp.test to your hosts file or run a local resolver such as dnsmasq. Django’s ALLOWED_HOSTS does not cause NXDOMAIN; it returns a different 400 error.
Conclusion
DNS_PROBE_FINISHED_NXDOMAIN means the domain could not be resolved. Visitors can usually fix it by flushing the DNS cache, switching DNS servers and turning off VPNs; site owners should check registration, nameservers and A records. Keep domains on auto-renew, audit records regularly and use sensible TTLs to avoid it in future.
