DNS_PROBE_FINISHED_NXDOMAIN means the browser asked DNS for a domain name and received an NXDOMAIN (“non-existent domain”) result. In practice, that can mean the address is misspelled or the site’s DNS is broken, but it can also be caused by a stale local DNS cache, a bad resolver, or network software that changes DNS traffic.
If only one site fails, check the address and the site first. If many unrelated sites fail on the same device or network, work through the fixes below in order.
DNS converts names such as example.com into IP addresses. The IETF defines NXDOMAIN as a response indicating that the queried domain name does not exist in DNS. You can read the technical definition in RFC 8020.
Retype the domain instead of relying on an old bookmark. Then open two or three unrelated sites. If everything else works, the problem is probably limited to that domain or its DNS records. If you own the site, check the registrar and authoritative DNS configuration rather than changing settings on every visitor’s device.
Also try the same domain in another browser. A second browser is useful for diagnosis, but it will not fix a genuine DNS failure.
Disconnect and reconnect Wi-Fi, then restart the computer or phone and the modem/router if you control it. On public Wi-Fi, make sure you have completed any sign-in portal. You can also briefly test a phone hotspot: if the site works there, the original network or its DNS resolver is the likely cause. Google’s current Chrome guidance likewise recommends checking the internet connection and restarting network equipment for loading errors.
Windows can retain negative DNS answers in its resolver cache. Microsoft documents ipconfig /flushdns specifically for clearing that cache during DNS troubleshooting.
ipconfig /flushdns.If you also have an IP-address problem, ipconfig /renew can renew a DHCP configuration, but it is not required for every NXDOMAIN error. See Microsoft’s ipconfig documentation.
If your ISP or router resolver is returning bad results, temporarily switching resolvers is a useful test. Google Public DNS uses 8.8.8.8 and 8.8.4.4 for IPv4. Record your existing DNS settings first so you can restore them later. Google provides current instructions for Windows, macOS, iOS, Android, ChromeOS, and routers in its Public DNS setup guide.
On current macOS releases, Apple’s path is System Settings > Network > your network service > Details > DNS. Apple documents adding or removing DNS servers in Mac network settings. On Android 9 or later, Google Public DNS can also be configured as Private DNS with the hostname dns.google.
On desktop Chrome, open More > Help > About Google Chrome, allow any update to install, and relaunch. Google’s Chrome update guide confirms that this page checks for updates.
Next, try the site in an Incognito window. If it works there, disable extensions from More > Extensions > Manage extensions, then re-enable them one at a time. Google specifically recommends this sequence for connection and loading errors.
A VPN, proxy, filtering client, or security product can override the system resolver or route DNS through another service. Disconnect it briefly and test again. On Windows 11, proxy controls are under Settings > Network & internet > Proxy. If turning the software off fixes the error, correct its DNS or proxy configuration instead of leaving protection disabled permanently.
If other browsers work on the same device but Chrome still fails, reset Chrome from Settings > Reset settings > Restore settings to their original defaults. Google notes that bookmarks and saved passwords are not deleted by this reset, although settings such as extensions, the startup page, and content settings are restored. See the official reset instructions.
Do not downgrade Chrome, download an old browser from a mirror site, disable IPv6 at random, or turn off antivirus protection as a routine fix. Those steps can create security or connectivity problems without correcting the DNS cause.
If every device on one network gets NXDOMAIN for valid domains, contact the ISP or network administrator. If only one domain fails everywhere, the site owner or DNS provider needs to correct its records. If only one device fails after the steps above, review that device’s hosts file, DNS-management software, firewall rules, and network adapter configuration.
For Chrome-specific loading problems, Google’s connection and loading error guide is the best current reference for the browser-side checks.
A practical 2026 guide to shoppable short videos, creator affiliates, and livestream shopping, with dated U.S. forecasts, platform examples, and a buyer checklist for disclosures and returns.
Compare 10 proxy browsers and browser tools, from Tor and Opera to Firefox and CroxyProxy, with practical privacy limits and setup advice.
Learn how to bulk delete Facebook posts on your phone, filter old updates, use Trash or Archive, and restore posts within 30 days.
Fix Chrome’s ERR_TUNNEL_CONNECTION_FAILED error by checking proxy and VPN settings first, then troubleshooting extensions, DNS, and security software.
See how Integrated Inbox brought Google apps into Gmail in Firefox, what still works on paper, and how Gmail’s built-in side panel compares.
Learn how WebFonter once let you try FontShop fonts on live websites, why the original tool is outdated, and how to preview typefaces today.
The old Facebook Undo extension offered a five-second delay. Learn what still works to edit, remove, archive, or restore an embarrassing Facebook post.
Use the Privacy Settings Firefox extension to change supported privacy preferences from a toolbar popup, plus learn when built-in controls work better.
See how Shrink2One originally grouped several URLs into a single short link, its optional password feature, and what to do if the service is unavailable.
Suspect unauthorized Gmail access? Check recent account activity, IP addresses, signed-in devices, and security events—and learn how to secure your account.
