DNS_PROBE_FINISHED_NO_INTERNET: Fix in 3 Steps

30-Second Fix: Flush the DNS Cache

This is the culprit 80% of the time. Your computer's DNS resolver has a stale or corrupted entry for the site you're trying to hit. Flush it and watch Chrome work again.

On Windows 10 or 11:

1. Open Command Prompt as admin — hit Win+R, type cmd, then hit Ctrl+Shift+Enter.
2. Run this command:

ipconfig /flushdns

You'll see "Successfully flushed the DNS Resolver Cache." No restart needed. Hit Chrome again. If the error's gone, you're done. Skip the rest.

On macOS (Ventura through Sequoia):

1. Open Terminal from Applications > Utilities.
2. Run:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Enter your admin password. You won't get a confirmation message — that's normal. Close Terminal and reload the page.

Why this works: DNS caches go bad when your ISP changes their records, or when a site moves to a new IP. Chrome holds onto the old IP and can't connect. Flushing forces a fresh lookup.

5-Minute Fix: Reset Network Stack (No Reboot)

If flushing didn't cut it, the problem isn't the cache — it's the adapter itself. Maybe you have a misconfigured IP or a corrupted Winsock catalog. Here's the full reset sequence for Windows. Mac users skip to the next section.

On Windows 10/11:

1. Open Command Prompt as admin again.
2. Run these commands one at a time, in order:

ipconfig /release
ipconfig /renew
netsh int ip reset
netsh winsock reset

The netsh commands will ask you to reboot — but don't. Not yet. Just close the command prompt and restart Chrome first. If the page loads, great. If not, reboot now.

When this matters: This fixes cases where you had a static IP set by a VPN or a network bridge that left orphaned routes. I've seen it happen after a corporate VPN disconnect — your adapter keeps the old DNS server IP, which no longer routes traffic.

On macOS:

1. Go to System Settings > Network.
2. Click your active connection (Wi-Fi or Ethernet), then click "Details".
3. Select "TCP/IP" and click "Renew DHCP Lease".
4. Then go to "DNS" tab, and remove any custom DNS servers except for 8.8.8.8 or 1.1.1.1. Hit OK.

This forces macOS to grab a fresh IP and a clean DNS server list. Don't skip removing custom DNS — that's a common trap from old VPN profiles.

15+ Minute Fix: Check the Real Culprit — Router or ISP

If you're still staring at the error, the problem's not local. It's either your router's DNS relay or your ISP's DNS servers. Here's how to nail it down.

Test with a different DNS server (takes 2 minutes):

1. Open your router's admin page — usually 192.168.1.1 or 192.168.0.1.
2. Log in (default credentials on the sticker).
3. Find the DNS settings. On a Netgear or TP-Link router, look under WAN or Internet settings. On an ASUS, it's under WAN > Internet Connection.
4. Change from "Get automatically from ISP" to "Use these DNS servers".
5. Set Primary to 8.8.8.8 and Secondary to 8.8.4.4 (Google). Or use 1.1.1.1 and 1.0.0.1 (Cloudflare). Apply.

Save the settings. Wait 30 seconds, then flush your PC's cache again (ipconfig /flushdns). Try the site.

Why this works: ISP DNS servers can be flaky — they drop queries under load or serve stale records. Google and Cloudflare are rock solid. I've seen ISPs like Comcast and Spectrum have widespread DNS issues that lasted hours. Switching DNS fixes it instantly.

Router reboot (5 minutes):

1. Unplug the router's power cable.
2. Wait a full 60 seconds — not 10, not 30. Sixty.
3. Plug it back in. Wait for all lights to settle (usually 2 minutes).

This clears any DNS proxy cache inside the router itself. Many consumer routers cache DNS to speed up lookups, and that cache can get corrupted the same way your PC's does. A power cycle is the only way to clear it safely.

Last resort: Check your hosts file for malware or VPN leftovers

Sometimes a rogue entry in C:\Windows\System32\drivers\etc\hosts (Windows) or /etc/hosts (Mac) maps a legitimate domain to a dead IP. Open the file in Notepad (Windows) or nano (Mac). Look for lines like 127.0.0.1 www.example.com or 0.0.0.0 example.com. If you didn't put them there, comment them out with a # at the start of the line. Save the file and flush DNS again.

When this happens: I've seen this after ad-blocking software like Pi-hole or uBlock Origin leaves behind redirect rules. Also common after trial VPN software that didn't clean up after itself. Check the file — it's a 30-second sanity check that's saved me hours.

Still broken? It's not DNS.

If none of this worked, you've got a deeper connectivity issue — likely a dead cable, a misconfigured VLAN, or a firewall rule blocking UDP port 53. That's beyond this guide. Call your ISP or your network team. But I'm betting the flush or the router DNS swap fixes it. Those two cover 95% of cases.