DNS_PROBE_FINISHED_NO_INTERNET: No usable internet connection for DNS
Also searched as: no internet DNS probe · DNS_PROBE_FINISHED_NO_INTERNET
Is DNS_PROBE_FINISHED_NO_INTERNET happening on your domain?
A check run from our infrastructure rather than your device confirms whether the domain resolves normally for everyone else.
Free, no signup. Runs from outside your network, which is the only way to tell a server fault from a local one.
Short answer
The DNS probe could not reach any resolver because there is no working route to the internet. The domain is irrelevant here — connectivity is the problem.
What DNS_PROBE_FINISHED_NO_INTERNET means
Chrome distinguishes 'the name failed' from 'the network failed'. This variant is the latter: the probe never reached a DNS server at all.
Causes and fixes, most likely first
The device is not actually online despite showing a connection.
Test a known-good site or run a connectivity check. A Wi-Fi association without DHCP looks connected but is not.
A captive portal is blocking traffic until sign-in.
Open any plain HTTP URL to trigger the portal, sign in, then retry.
A firewall is blocking outbound port 53.
Allow outbound DNS, or configure the device to use DNS over HTTPS which travels over 443.
How to stop it happening again
- •Nothing server-side prevents this; it is a client connectivity condition.
Frequently asked questions
Why does this show when I clearly have internet?
Because reaching Wi-Fi is not the same as reaching the internet. A captive portal, failed DHCP, or blocked port 53 all produce this state.