When a name will not resolve, Chrome runs a quick test: it asks your usual DNS and Google’s public DNS about google.com. If Google’s works and yours does not, you see BAD_CONFIG — the problem is your DNS settings. If neither answers, NO_INTERNET. Either way it is the device or network, not the site.
This site can’t be reached example.com’s server IP address could not be found. DNS_PROBE_FINISHED_BAD_CONFIG
How 3 other clients word the same error
Chrome, no connection
No internet DNS_PROBE_FINISHED_NO_INTERNET
Chrome, with Secure DNS
Check your Secure DNS settings DNS_PROBE_FINISHED_BAD_SECURE_CONFIG
Chrome, still testing
example.com’s DNS address could not be found. Diagnosing the problem. DNS_PROBE_POSSIBLE
| Error | DNS_PROBE_FINISHED_BAD_CONFIG |
| Usually fixed by | The visitor’s device or network |
| Shown by | Chrome and Edge, after a failed lookup |
| BAD_CONFIG | Your DNS fails, Google Public DNS works |
| NO_INTERNET | Google Public DNS cannot be reached either |
| BAD_SECURE_CONFIG | Same as BAD_CONFIG, with Secure DNS set to a custom provider |
Look up the domain’s DNS
Look the name up from outside your network: if it resolves here, the problem is your device, network or DNS settings.
What it means
After a lookup fails, Chrome asks two resolvers about google.com — the one your device uses, and Google Public DNS (8.8.8.8) — to tell a broken site from a broken connection. The code on the page is the result: BAD_CONFIG when only your resolver fails, NO_INTERNET when both fail, BAD_SECURE_CONFIG when the failing resolver is a Secure DNS (DNS over HTTPS) provider you chose, and POSSIBLE while the test is still running.
NXDOMAIN is the other result — your resolver works and the name really does not exist — and has its own page.
Why it happens
- The DNS server your router or network hands out is down or misbehaving.
- A DNS server typed by hand in the device’s network settings that no longer works.
- A custom Secure DNS provider in Chrome that cannot be reached — Chrome does not fall back from a custom provider.
- A VPN, firewall or security software blocking DNS, or no connection at all.
How to fix it
- Restart the router and reconnect to the network.
- Switch the device’s DNS to automatic, or to a public resolver (1.1.1.1, 8.8.8.8), and flush the DNS cache: ipconfig /flushdns on Windows, resolvectl flush-caches on Linux.
- In Chrome, open Settings → Privacy and security → Security → Use secure DNS, and switch a custom provider back to automatic or off.
- Turn off a VPN or firewall briefly to see if it is the cause.
If you are visiting the site
- Everything above is on your side — if the site loads from another network or device, the site is fine.
See it for yourself
nslookup google.com
nslookup google.com 8.8.8.8
The same test Chrome runs: if the second works and the first does not, your DNS settings are the problem.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- Dns probe service factory.cc — raw.githubusercontent.com
- Error page strings.grdp — raw.githubusercontent.com
- Manage Chrome safety and security — support.google.com
- ipconfig — learn.microsoft.com