DNS_PROBE_FINISHED_NO_INTERNET: What It Means and How to Fix It

You open Chrome, load a page, and get DNS_PROBE_FINISHED_NO_INTERNET instead of the site. It is one of the most common Chrome connection errors. It is also one of the most fixable.

The message looks alarming, but it points to a narrow set of causes. Most live in your browser, your device’s network settings, or your router. The website itself is rarely the problem.

This guide does two things. First, it shows you how to isolate where the fault sits in under a minute. Then it walks the exact fixes for Chrome, Windows, macOS, Linux, and mobile. The order matches what a network technician would try first.

What DNS_PROBE_FINISHED_NO_INTERNET means

DNS_PROBE_FINISHED_NO_INTERNET means Chrome ran a DNS probe, finished it, and found no working internet path to resolve the address. Your device could not turn the domain name into an IP and reach it. The fault is on your side, not the website.

Every web request starts with a DNS lookup. Your browser asks a DNS server to translate a name like example.com into an IP address. Our guide on how DNS works walks through that handshake step by step.

When that lookup cannot complete over a usable connection, Chrome stops and shows this error. The “probe finished” wording means Chrome tested the connection and gave up. The “no internet” wording means it never found a working path.

Edge shows the same error because it shares Chrome’s Chromium engine. Firefox and Safari hit the same wall but word it differently. The message is browser-specific, but the cause usually is not.

First, isolate it: browser, device, or network?

Before changing settings, find where the fault lives. Three quick tests do it: open a second browser, load a site on a second device, then try mobile data. Each result narrows the cause to your browser, that one device, or the whole network.

This step saves time. Most people start resetting things at random and fix nothing. A few seconds of testing tells you exactly which fix list to use.

If every browser and every device fails on the same network, the cause is shared. That points at your router, your DNS settings, or your internet provider. The upstream section below covers those.

Browser-level fixes (Chrome and Edge)

If only one browser fails, fix it there. Clear Chrome’s own DNS cache, flush its socket pools, disable extensions, and toggle Secure DNS. These steps reset the browser’s private network state without touching your device or router settings.

Clear Chrome’s host cache and sockets

Chrome keeps its own DNS cache, separate from your operating system. Stale entries there cause this error even when the rest of your device is fine.

1. Go to chrome://net-internals/#dns and click Clear host cache.
2. Go to chrome://net-internals/#sockets and click Flush socket pools.
3. Reload the page you were trying to reach.

Disable extensions and test

Ad blockers, VPN add-ons, and security extensions can block DNS requests. Open chrome://extensions/ and turn them all off. If the page loads, re-enable them one at a time to find the culprit.

Toggle Chrome’s Secure DNS

Chrome’s Secure DNS feature, also called DNS over HTTPS, routes lookups through an encrypted resolver. A misconfigured provider here can break resolution and trigger the error.

1. Open Settings → Privacy and security → Security.
2. Find Use Secure DNS. Turn it off, then reload the page.
3. If that works, turn it back on and pick a named provider like Google or Cloudflare instead of your default.

Fix it on Windows

If the whole device fails, reset its network stack. On Windows, flush the DNS cache, release and renew your IP, then rebuild Winsock and the TCP/IP stack. Run the commands in an elevated Command Prompt, then restart the computer to apply them cleanly.

Open the Start menu, type cmd, right-click Command Prompt, and choose Run as administrator. Then run each command below in order.

Flush DNS and renew your IP address

ipconfig /flushdns
ipconfig /release
ipconfig /renew
ipconfig /registerdns

The first command clears stale name records. The next two drop and reacquire your IP from the router. The last one re-registers your device with DNS.

Reset Winsock and the TCP/IP stack

If the error survives a flush, the network stack itself may be corrupted. These two commands rebuild it. Restart the computer afterward.

netsh winsock reset
netsh int ip reset

Winsock is the layer that lets apps use the network. Resetting it clears bad entries left by malware, old VPN clients, or failed updates.

Check the DNS Client service and your driver

A stopped DNS Client service blocks all name resolution. Press Win + R, type services.msc, and confirm DNS Client is running. If your network driver is outdated, update it through Device Manager.

Fix it on macOS, Linux, and mobile

The same logic applies beyond Windows: flush the resolver cache, then set a reliable DNS server. The commands differ by system, and phones use a settings menu instead of a terminal. Pick the steps that match your device below.

macOS

Open Terminal and run the flush command. It clears the system resolver cache on current macOS versions.

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux (systemd-resolved)

Most modern distributions use systemd-resolved. Flush its cache with one command.

sudo resolvectl flush-caches

On older systems, use sudo systemd-resolve --flush-caches instead. If you run dnsmasq, restart that service.

Android and iOS

Phones cache DNS too. The fastest reset is to toggle Airplane Mode on and off. For a lasting fix, set a trusted DNS provider:

• Android 9 and newer: Settings → Network & internet → Private DNS → enter dns.google.
• iOS: Settings → Wi-Fi → tap the (i) by your network → Configure DNS → Manual → add 1.1.1.1.

Switch to a public DNS server — and test it first

Your provider’s DNS server may be slow, down, or misconfigured. Switching to a public resolver like Google or Cloudflare often clears the error outright. Test resolution before and after, so you know the change actually fixed the lookup.

The two most reliable free resolvers are Google Public DNS and Cloudflare. Either works for home use.

• Google: 8.8.8.8 and 8.8.4.4
• Cloudflare: 1.1.1.1 and 1.0.0.1

On Windows, open Network and Sharing Center → Change adapter settings. Right-click your connection, open Properties, select Internet Protocol Version 4, and enter the addresses above. Setting DNS on the router applies it to every device at once.

Confirm the fix instead of guessing. Run a query with our DNS lookup tool to check that a domain now resolves to an IP. If you recently changed a domain’s records, our DNS propagation checker shows whether resolvers worldwide have caught up.

The DNS_PROBE error family, compared

Chrome shows several DNS_PROBE errors, and each points at a different failure. Telling them apart saves you from trying the wrong fix. NO_INTERNET means no path to a resolver. NXDOMAIN means the name does not exist. The table below maps each one.

All of these sit under Chrome’s generic “This site can’t be reached” banner. The DNS_PROBE suffix is the specific reason. Match your error to the row below.

When the problem is upstream: router, ISP, and Windows updates

If every device on the network shows the error, the fix is not on your computer. The cause is usually your router, your internet provider, or a recent operating-system update that changed network defaults. Work outward from the router to the line.

Reboot the router and modem

Power-cycle both. Unplug them, wait 30 seconds, then plug the modem in first and the router second. This clears stale leases and a hung connection to your provider. It resolves a large share of whole-network failures.

Watch for update-driven DNS regressions

Windows updates sometimes reset or break DNS behavior. Users report the error appearing right after an update, on machines that worked for months. If that matches your timeline, the network-stack reset in the Windows section is your fix.

Rule out the provider

If a reboot and a public DNS change both fail, the issue may be upstream. Check whether your provider reports an outage. Our network connectivity troubleshooting guide covers how to confirm the fault sits past your modem.

Related Tools & Resources

NetworkCheckr hosts the free tools these fixes call for, so you can test DNS resolution yourself instead of guessing. Use the resolver checks below to confirm a fix worked, and the guides to understand the system behind the error.

Frequently Asked Questions

Short answers to the questions people ask most about DNS_PROBE_FINISHED_NO_INTERNET. Each one expands on a point from the fixes above. Together they cover what the error means, where it comes from, and how related DNS errors differ.