Is DNS_PROBE_FINISHED_NO_INTERNET the same as NXDOMAIN?

No, and the difference tells you where to look. DNS_PROBE_FINISHED_NXDOMAIN means a resolver came back with an authoritative 'no such domain' — the lookup completed and the name doesn't exist. NO_INTERNET means Chrome's own connectivity probe couldn't reach anything at all, so it stopped blaming the domain and blamed your connection. One points at the site; the other points at the link between your machine and the internet.

Every site fails, not just one — so why does the error say DNS?

Because of how Chrome fails. When a navigation fails, Chrome runs a background DNS probe against a known host to figure out why. If that probe also can't get through, Chrome shows a DNS-flavored error even though the real problem is that nothing is reaching the network. Read NO_INTERNET as 'no working internet, starting with DNS' rather than 'this domain's DNS is broken.'

It loads on my phone but not my laptop. Whose fault is that?

The internet and the site are fine — your laptop is the outlier. Compare the two devices directly: are they on the same Wi-Fi? Is a VPN running on the laptop only? Is Chrome's Secure DNS (DNS-over-HTTPS) set to a provider the laptop can't reach? Is a firewall or antivirus on the laptop filtering DNS? The fault is in the laptop's network stack, resolver, or a piece of software sitting between Chrome and the wire.

Views: 103

DNS_PROBE_FINISHED_NO_INTERNET Fix

DNS_PROBE_FINISHED_NO_INTERNET in Chrome? Confirm the site resolves publicly, then isolate your network, resolver, or VPN. Free instant check, no sign-up.

Check your domain for this issue now

Free, no sign-up. Runs the exact check this guide describes and shows what to fix.

Problem

Chrome refuses to load any page and shows DNS_PROBE_FINISHED_NO_INTERNET with a “No internet” message. Reloading doesn’t help, and it usually happens on every site at once, not just one.

Symptoms

Chrome shows DNS_PROBE_FINISHED_NO_INTERNET on every site, not a single domain.
The Wi-Fi or Ethernet icon may still look “connected,” but nothing loads.
Other apps (email client, messenger) are also stuck or timing out.
A different device on the same network works fine — or fails the same way.
Toggling Wi-Fi off and on, or reconnecting, sometimes clears it briefly.

What This Error Actually Means

The wording blames DNS, but DNS_PROBE_FINISHED_NO_INTERNET is really Chrome’s way of saying nothing is getting to the internet. When a page fails to load, Chrome doesn’t just surface the raw error — it runs a background DNS probe against a known host to diagnose the failure. If even that probe can’t complete, Chrome concludes there’s no working connection and reports the “no internet” variant.

That’s the key insight, and it flips where you look. DNS_PROBE_FINISHED_NXDOMAIN means a resolver answered and the name doesn’t exist — that’s about the domain. DNS_PROBE_FINISHED_BAD_CONFIG means your local DNS setup is broken but the network is otherwise up. NO_INTERNET means the probe couldn’t reach anything at all, so the problem is almost always your side of the wire: the network path, the resolver you were handed, or something local intercepting traffic.

Which is why the fastest diagnosis is to check the domain from outside your network. If the site resolves cleanly from a public resolver, its DNS is healthy and the fault is between your machine and the internet — not the website.

Top 3 Causes

No working network path - The Wi-Fi or Ethernet link dropped, a captive portal (hotel, café, airport) hasn’t been passed yet, or the router lost its upstream connection. The device thinks it’s “connected” to the local network but has no route to the internet.
A broken or missing resolver - DHCP handed out no DNS server or a dead one, a static DNS entry points at a resolver that’s gone, or Chrome’s Secure DNS (DNS-over-HTTPS) is set to a provider your network can’t reach. The link is up but name resolution has nowhere to go.
Something local is intercepting DNS - A VPN with a dead tunnel, a firewall or antivirus blocking port 53 (or DoH), or stale hosts entries. Traffic leaves the browser and never comes back.

Diagnose with DechoNet

DNS Lookup to resolve the domain from outside your network. If it answers with valid records, the domain and its DNS are fine — the failure is local, so stop debugging the website and start on your own connection.
DNS Propagation to confirm the same records resolve consistently across public resolvers, ruling out any real server-side DNS problem before you spend time on your router.

Resolution Checklist

Confirm it’s every site, not one. If a single domain fails but others load, this isn’t NO_INTERNET — look at that domain’s DNS instead.
Check the physical link: is Wi-Fi actually connected? On a public network, open any page to trigger the captive portal login.
Restart the router/modem and reconnect. This re-runs DHCP and often restores a working resolver in one step.
Renew your address: ipconfig /release then ipconfig /renew (Windows), or toggle Wi-Fi off/on (macOS). Flush DNS with ipconfig /flushdns or sudo dscacheutil -flushcache.
Turn off any VPN and test. A dead or misconfigured tunnel is a common cause of “connected but no internet.”
In Chrome, check Settings → Privacy and security → Use Secure DNS. If it’s set to a specific provider, switch it to “off” or to your system resolver and retry.
Temporarily set a public resolver (8.8.8.8 / 1.1.1.1) at the OS level. If that fixes it, the DHCP-assigned resolver was the problem.
Disable firewall/antivirus web protection briefly to see if it’s filtering DNS. Re-enable it and adjust the rule once confirmed.

When to Escalate

If every device on the network fails identically, the problem is upstream — the router or the ISP link, not your machine. Check the router’s status page or call the ISP.
On a managed or corporate machine, DNS, VPN, and firewall settings may be locked by policy. A Secure DNS or split-tunnel VPN misconfiguration pushed centrally has to be fixed by IT, not on the device.