When a website fails to load and Chrome displays the error message DNS_PROBE_FINISHED_NXDOMAIN, it means the browser completed its DNS lookup but the domain name could not be found. The problem is rarely a virus and often fixable within minutes by clearing cached data, adjusting network settings, or switching DNS servers. This guide covers the meaning of the error, step-by-step fixes for Chrome, Mac, Android, and Edge, as well as community-tested solutions.
The error appears across browsers built on Chromium—Chrome, Edge, Brave—and can also occur on mobile devices. While the message looks technical, the underlying cause is usually a temporary glitch in the DNS resolution chain. Understanding what it means helps narrow down the fix.
Below, we break down the error, provide a quick-reference overview, and walk through solutions for the most common platforms.
What Does DNS_PROBE_FINISHED_NXDOMAIN Mean?
A browser error indicating the domain name could not be resolved to an IP address – the DNS server responded that the domain does not exist.
Websites fail to load; the error appears in Chrome, Edge, or other browsers; other devices on the same network may work fine.
Flush your DNS cache, restart the router, or switch to a public DNS like Google 8.8.8.8 or Cloudflare 1.1.1.1.
Usually harmless and not a virus. If the error persists across multiple networks, check ISP or router settings or scan for malware that may alter DNS.
Understanding the NXDOMAIN Response
NXDOMAIN stands for “non-existent domain.” It is a standard DNS response code that tells the requester that the queried domain name does not exist in the DNS records. When Chrome displays DNS_PROBE_FINISHED_NXDOMAIN, it means the DNS probe ran to completion and received that NXDOMAIN answer. According to Cloudflare Developers, “DNS_PROBE_FINISHED means that the DNS probe ran to completion and NXDOMAIN stands for non-existent domain.”
Common Causes of the Error
The error can be triggered by a mistyped URL, a temporary DNS server glitch, a stale local DNS cache, incorrect DNS server settings, IPv6 misconfiguration, or interference from VPN, proxy, firewall, or antivirus software. In rare cases, an incorrect entry in the hosts file can also cause it. Google Chrome Help explains that the error means “your computer was able to reach the DNS server, but the server reported that the domain does not exist.”
Key Insights About DNS_PROBE_FINISHED_NXDOMAIN
- Clearing DNS cache resolves the error in most cases within seconds.
- Chrome’s “Use secure DNS” setting (Cloudflare 1.1.1.1) can sometimes cause NXDOMAIN errors for legitimate sites.
- The error name literally means the DNS probe ran to completion and found that the domain does not exist (NXDOMAIN).
- Many Reddit users report success by disabling IPv6 or turning off VPN temporarily.
- The error is browser-agnostic but most frequently reported in Chrome due to its user base.
Key Facts About DNS_PROBE_FINISHED_NXDOMAIN
| Attribute | Details |
|---|---|
| Error Name | DNS_PROBE_FINISHED_NXDOMAIN |
| Interpretation | DNS probe finished – Non-Existent Domain |
| Primary Cause | Domain name cannot be resolved to an IP address |
| Common Browsers | Chrome, Edge, Brave (uses Chromium); also Firefox (different error code) |
| Frequency | Common; can happen sporadically or persistently |
| Security Risk | Low – not a malware infection, but could indicate a DNS hijacking in rare cases |
| Quickest Fix | Flush DNS cache (cmd: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on Mac) |
How to Fix DNS_PROBE_FINISHED_NXDOMAIN: General Steps
Step 1: Check the URL and Test Other Websites
Confirm the spelling, subdomain, and top-level domain are correct. If only one site is affected, the domain may be temporarily down. Test other websites to determine whether the problem is site-specific or network-wide. As IONOS advises, this is the first logical step before touching any settings.
Step 2: Flush DNS Cache
Flushing the local DNS cache clears outdated or corrupted records. On Windows, open Command Prompt as administrator and run ipconfig /flushdns. On macOS, open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. For Chrome itself, navigate to chrome://net-internals/#dns and click “Clear host cache.” Hostinger notes that this fix works for many users instantly.
Always flush the operating system DNS cache first, then the browser’s internal cache. On Windows 11, Microsoft also recommends netsh int ip reset and netsh winsock reset if flushing alone does not work (Microsoft Support).
Step 3: Restart Router and Device
A simple power cycle of the router and modem clears temporary network issues that may interfere with DNS resolution. Wait 30 seconds before turning them back on. Also restart your computer or mobile device to refresh network connections.
Step 4: Change DNS Server Settings
Switching to a public DNS resolver can bypass problems with your ISP’s DNS. The most commonly recommended options are Google DNS (8.8.8.8 and 8.8.4.4) and Cloudflare DNS (1.1.1.1). Instructions vary by operating system: on Windows, go to Network Settings → Change adapter options → IPv4 properties. On macOS, go to System Settings → Network → Advanced → DNS. After changing the DNS server, flush the cache again.
How to Fix DNS_PROBE_FINISHED_NXDOMAIN on Chrome
Disable or Adjust Secure DNS in Chrome
Chrome’s “Use secure DNS” feature, enabled by default in many versions, can sometimes cause false NXDOMAIN responses. Go to chrome://settings/security and under “Use secure DNS,” either set it to “Automatic” or choose a custom provider like Google (8.8.8.8). If the error persists, try turning secure DNS off temporarily. IONOS and Hostinger both mention this step.
Clear Chrome’s Internal DNS Cache
Chrome maintains its own DNS cache separate from the OS. To clear it, type chrome://net-internals/#dns in the address bar and click “Clear host cache.” You can also clear all cached data via Settings → Privacy and security → Clear browsing data (select “Cached images and files”). Jetpack confirms this method.
Reset Chrome Flags (Experimental Features)
Experimental flags in Chrome (chrome://flags) can interfere with DNS handling. If you have enabled any flags, reset them to default by clicking “Reset all.” Restart Chrome afterward.
How to Fix DNS_PROBE_FINISHED_NXDOMAIN on Mac
Flush DNS Cache on macOS
Open Terminal and enter sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Enter your administrator password when prompted. The commands flush both the DNS cache and restart the mDNSResponder process. Hostinger and Kinsta both recommend this as the primary Mac fix.
Check Wi-Fi and Network Settings
If flushing the cache does not resolve the error, go to System Settings → Network → Wi-Fi, click Details, then DNS. Remove any manually entered DNS servers and try using automatic settings, or add Google DNS (8.8.8.8). Also disable any active VPN or proxy services temporarily, as these can intercept DNS queries.
The flush command above works for macOS Ventura, Monterey, and Big Sur. Earlier versions may require slightly different commands, but the same principle applies.
How to Fix DNS_PROBE_FINISHED_NXDOMAIN on Android and Mobile
Clear DNS Cache on Android (Chrome)
In Chrome for Android, open Settings → Privacy and security → Clear browsing data and check “Cached images and files.” Also go to Chrome’s security settings and set “Use secure DNS” to Automatic. Google Chrome support suggests this approach for Android-related DNS probe issues.
Change Network or Disconnect VPN
If the error appears only on mobile data or a specific Wi-Fi network, try switching networks. Disable any VPN app temporarily, as VPNs can alter DNS routing. Restart the phone to refresh network caches.
Top DNS_PROBE_FINISHED_NXDOMAIN Fixes from Reddit
While no single Reddit thread is cited here, community forums consistently recommend the following steps based on aggregated user reports:
Using Command Prompt to Flush DNS (Windows)
Windows users frequently report success by running ipconfig /flushdns as administrator, followed by ipconfig /registerdns and netsh winsock reset. Restart the PC after these commands.
Disabling IPv6 on Network Adapter
IPv6 misconfiguration can cause DNS resolution failures. In Windows, go to Network Settings → Change adapter options → right-click your connection → Properties → uncheck “Internet Protocol Version 6 (TCP/IPv6)” and click OK. Reboot and test.
Temporarily Turning Off Antivirus or Firewall
Security software with DNS filtering may block legitimate lookups. Disable the antivirus or firewall temporarily to see if the error disappears. If it does, add an exception for the affected website or adjust DNS filtering settings.
Troubleshooting Steps in Order (From Simple to Advanced)
- Check if the error appears on other websites – If only one site is affected, the domain may be down.
- Restart your router and modem – Clears temporary network issues.
- Flush DNS cache on your device – Windows:
ipconfig /flushdns; Mac:sudo dscacheutil -flushcache; Chrome:chrome://net-internals/#dns. - Change DNS server to a public resolver – Set to Cloudflare 1.1.1.1 or Google 8.8.8.8.
- Disable IPv6 temporarily – May resolve misconfigured IPv6 records.
- Turn off VPN, proxy, or security software – Third-party filters can interfere with DNS lookups.
Clarifying Certainty vs. Uncertainty
| Established Information | Information That Remains Unclear |
|---|---|
| The error always means the DNS probe completed and the domain was not found at the DNS level. | The error is not a virus, but it could be a symptom of a DNS hijack if it persists across networks and devices. |
| Flushing the DNS cache and restarting the router resolves the error in the vast majority of cases. | Secure DNS (DoH) in Chrome is generally safe, but in rare cases it can cause false NXDOMAIN for valid sites. |
Why This Happens: Technical Context
DNS_PROBE_FINISHED_NXDOMAIN is a Chrome-specific error message for Chromium browsers. When you type a URL, the browser performs a DNS lookup (the “probe”). If the DNS server responds with NXDOMAIN (non-existent domain), the probe finishes and the error appears. The root cause can be a mistyped URL, a temporary DNS server glitch, a stale local DNS cache, or a network configuration issue—such as incorrect DNS server settings or IPv6 misconfiguration. It does not necessarily mean the website is down; your local resolver may simply have outdated or incorrect records.
Authoritative Sources and Quotations
DNS_PROBE_FINISHED_NXDOMAIN means your computer was able to reach the DNS server, but the server reported that the domain does not exist.
— Google Chrome Help
DNS_PROBE_FINISHED means that the DNS probe ran to completion and NXDOMAIN stands for non-existent domain. Together, these messages mean that the DNS resolution was successful but the name does not exist.
— Cloudflare Developers
The DNS_PROBE_FINISHED_NXDOMAIN error appears when your browser can’t find a website’s IP address. In simple terms, the domain name isn’t resolving properly.
— Hostinger Tutorials
What to Do If the Error Persists
If all general steps have been tried and the error continues, consider contacting your ISP to check for DNS outages or restrictions. Test on a different network (e.g., a mobile hotspot) to isolate equipment issues. Run a malware scan to rule out software that may alter DNS settings. For advanced users, use tools like nslookup or dig to manually query the domain and compare results with expected IP addresses.
Frequently Asked Questions
DNS_PROBE_FINISHED_NXDOMAIN on Edge?
Edge is built on Chromium, so the same fixes apply: flush DNS, clear browser cache, disable secure DNS, or reset network settings.
www.googleadservices.com DNS_PROBE_FINISHED_NXDOMAIN
This specific domain is used by Google for advertising services. The error may occur due to ad blockers, privacy filters, or DNS-level blocking. Try disabling extensions or using a different DNS.
Is DNS_PROBE_FINISHED_NXDOMAIN a virus?
No, it is a standard DNS error. However, malware that modifies DNS settings can cause similar errors, so run a security scan if you suspect infection.
Why do I keep getting DNS_PROBE_FINISHED_NXDOMAIN after updating Chrome?
A Chrome update may reset DNS settings or enable secure DNS by default. Check chrome://settings/security and ensure “Use secure DNS” is set to your preference.
DNS_PROBE_FINISHED_NXDOMAIN on Windows 11?
Windows 11 treats DNS similarly to Windows 10. Use Command Prompt as administrator and run ipconfig /flushdns, then restart the browser.
What does NXDOMAIN stand for?
Non-Existent Domain – a standard DNS response code indicating the queried domain name does not exist in the DNS records.
Does Chrome’s secure DNS cause the error?
In rare cases, yes. Try setting secure DNS to Automatic or disabling it temporarily from chrome://settings/security.
How to clear DNS cache on Mac?
Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
Can a VPN cause DNS_PROBE_FINISHED_NXDOMAIN?
Yes, VPNs can redirect DNS queries and cause lookup failures. Disconnect the VPN to test.
What if the error appears on all devices?
The issue likely lies with the router or ISP. Restart the router and contact your ISP if the error persists.
For more detailed instructions on clearing DNS cache across platforms, see How to Clear DNS Cache on Windows, Mac, and Chrome. If you encounter other browser errors, our guide on Common Chrome Browser Errors and Fixes may help.
Henry William Morgan Harrison is a staff writer for NorwichWire.co.uk, covering local news, council decisions, business and community stories across Norwich and Norfolk. He works under Editor-in-Chief William Hargreaves and Managing Editor Clara Benson, following the newsroom standards for sourcing, verification and fact-checking set out in our editorial policies.