DNS Probe Finished No Internet Fix Step-by-Step Solutions That Actually Work

You open Chrome, type in a URL, and get hit with DNS_PROBE_FINISHED_NO_INTERNET — a frustrating error that usually means Chrome tried to resolve a domain name and came back empty-handed. The confusing part is that your Wi-Fi indicator shows you are connected. The problem is almost never your internet connection itself; it is nearly always a DNS resolver issue, a corrupted DNS cache, or a misconfigured network adapter. This guide walks through every proven fix in order of likelihood, with exact commands and clicks so you can stop guessing and start browsing again.

What DNS_PROBE_FINISHED_NO_INTERNET Actually Means

When Chrome loads a page it first asks your operating system to convert the domain name (for example, example.com) into an IP address. Your OS sends that query to a DNS resolver — usually the one assigned by your router via DHCP. If that resolver fails to respond, responds with an error, or your local DNS cache returns stale data, Chrome reports DNS_PROBE_FINISHED_NO_INTERNET. It is different from DNS_PROBE_FINISHED_NXDOMAIN (which means the domain does not exist) — this error means the DNS lookup process itself broke down entirely.

Common root causes include:

• A corrupted or oversized local DNS cache on your PC or Mac
• Your ISP's DNS server being slow, rate-limiting you, or temporarily offline
• A misconfigured or stuck DHCP lease assigning a bad DNS address
• A Chrome internal DNS cache that disagrees with the OS cache
• Firewall, antivirus, or VPN software intercepting DNS queries
• An incorrect static DNS entry typed into your network adapter settings
• IPv6 DNS misconfigurations causing fallback failures

Fix 1: Flush Your DNS Cache (Windows)

This is the single most effective fix and takes under 30 seconds. Open Command Prompt as Administrator — press Win + S, type cmd, right-click Command Prompt, and choose Run as administrator. Then run these commands one at a time:

After the last command, restart your PC. The flushdns command clears the local resolver cache. The release and renew commands drop your current DHCP lease and request a fresh one — which also pulls new DNS server addresses from your router. The winsock reset repairs the Windows network stack, which can get corrupted by VPN clients or aggressive antivirus software.

Fix 2: Flush the DNS Cache on macOS

Open Terminal (Cmd + Space, type Terminal, press Enter) and run the command appropriate for your macOS version:

You will be prompted for your password. After running the command, close and reopen Chrome and try again. If your Mac is on a corporate network with a managed DNS profile, the issue may reappear until the underlying profile is corrected.

Fix 3: Clear Chrome's Internal DNS Cache

Chrome maintains its own DNS cache entirely separate from the OS. Even after flushing the system cache, Chrome can still serve stale or broken entries. To clear it, paste this into Chrome's address bar and press Enter:

Click the Clear host cache button. Then navigate to the Sockets tab in the same page:

Click Flush socket pools. These two steps wipe Chrome's DNS and connection state completely. Reload the page that was failing — this fixes the error in roughly 30% of cases where the OS flush alone did not work.

Fix 4: Change Your DNS Server to a Public Resolver

If your ISP's DNS server is the problem, switching to a reliable public resolver like Google (8.8.8.8 / 8.8.4.4) or Cloudflare (1.1.1.1 / 1.0.0.1) usually resolves the error immediately.

Windows 10 and 11

1. Press Win + R, type ncpa.cpl, press Enter.
2. Right-click your active network adapter (Ethernet or Wi-Fi) and choose Properties.
3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
4. Choose Use the following DNS server addresses.
5. Set Preferred DNS to 1.1.1.1 and Alternate DNS to 1.0.0.1 (Cloudflare) or use 8.8.8.8 / 8.8.4.4 (Google).
6. Click OK, then close all dialogs.

macOS

1. Open System Settings (or System Preferences on older macOS) and go to Network.
2. Select your active connection and click Details (or Advanced on older versions).
3. Go to the DNS tab.
4. Remove any existing DNS entries and add 1.1.1.1 and 1.0.0.1.
5. Click OK and then Apply.

Android

On Android 9 and later, go to Settings > Network & Internet > Advanced > Private DNS. Switch from Automatic to Private DNS provider hostname and enter one.one.one.one (Cloudflare's DNS-over-TLS hostname). Tap Save.

Fix 5: Change DNS on Your Router

If multiple devices on your network all show the same error, the problem is almost certainly your router's upstream DNS setting. Changing DNS at the router level fixes all devices at once without touching each one individually.

Finding Your Router Admin Page

• ASUS routers: asusrouter.com or 192.168.1.1
• TP-Link: tplinkwifi.net or 192.168.0.1
• Netgear: routerlogin.net or 192.168.1.1
• D-Link: 192.168.0.1
• Linksys: 192.168.1.1

Log in with your admin credentials (default is often admin/admin or printed on the router label). Navigate to WAN Settings or Internet Settings depending on your router brand. Look for a DNS field — it may say "Primary DNS" and "Secondary DNS". Enter 1.1.1.1 as primary and 1.0.0.1 as secondary. Save and reboot the router. After it comes back online, reconnect your devices and test.

Fix 6: Disable IPv6 on Your Network Adapter

IPv6 DNS mismatches cause this error more often than people realize, especially on networks where the router does not fully support IPv6 but Windows keeps trying to use it. Disabling IPv6 on the adapter forces all DNS traffic over IPv4, which is typically more reliable in home environments.

In Windows, go back to ncpa.cpl, right-click your adapter, choose Properties, and uncheck Internet Protocol Version 6 (TCP/IPv6). Click OK. You do not need to restart — test immediately in Chrome.

Fix 7: Reset the Network Stack (Windows)

If flushing DNS did not work, the Windows TCP/IP stack itself may be corrupted. Run these commands in an elevated Command Prompt:

Then reset the full stack:

Restart the PC after running all of these. The resetlog.txt file will be created in your current directory and shows exactly what was changed — useful if you need to report the issue to IT support.

Fix 8: Check VPN and Security Software

VPN clients, endpoint security products, and some antivirus suites install virtual network adapters and redirect DNS traffic through their own resolvers. If that resolver goes down or is blocked by a firewall rule, you get DNS_PROBE_FINISHED_NO_INTERNET even though your physical connection is fine.

The diagnostic step is simple: disable your VPN and antivirus temporarily and reload the failing page. If it loads, the security software is the cause. Common offenders include Norton, Kaspersky, Avast with "Web Shield" enabled, and corporate VPN clients like Cisco AnyConnect or GlobalProtect. Check your VPN's DNS leak settings and make sure it is configured to use a reliable DNS resolver rather than a custom internal one that is unreachable from your location.

How to Verify Your DNS Is Working After the Fix

Do not just reload the page — actually confirm your DNS is resolving correctly. In Windows Command Prompt or Mac Terminal, run:

The first command uses your default resolver. The second explicitly tests Cloudflare's public DNS. If both return an IP address, DNS is healthy. If the first fails but the second succeeds, your default DNS server is the problem — switch to 1.1.1.1 permanently using Fix 4 above.

You can also use the DNS Lookup tool on this site to query any domain and see what DNS records are being returned in real time, which is especially helpful for confirming that your resolver is not returning empty or incorrect results.

Preventing the Error From Coming Back

The most reliable long-term fix is to stop relying on your ISP's DNS servers. ISP resolvers are often the weakest link — they are the first to go down during outages, they may throttle queries, and they frequently have slower response times than public alternatives.

• Set DNS at the router level using Cloudflare (1.1.1.1) or Google (8.8.8.8) so every device on your network benefits automatically.
• Enable DNS-over-HTTPS (DoH) in Chrome under Settings > Privacy and Security > Security > Use secure DNS. Select Cloudflare or Google from the dropdown. This encrypts DNS queries and bypasses ISP-level DNS failures entirely.
• Keep your router firmware updated. Outdated firmware is a common cause of DHCP/DNS assignment bugs that corrupt the DNS addresses pushed to your devices.
• Avoid third-party DNS accelerators that some ISPs bundle as optional software — they often do more harm than good and can silently redirect or block queries.
• Schedule a monthly router reboot. Routers accumulate DNS state over time. A clean reboot clears the internal resolver cache and reestablishes clean upstream connections.

When the Error Is Not Your Fault

Occasionally DNS_PROBE_FINISHED_NO_INTERNET is caused by a genuine outage at your ISP or at a major DNS provider. Before spending an hour troubleshooting, do a quick sanity check: open your phone (on cellular, not Wi-Fi) and try loading the same URL. If it loads fine on cellular but not on your home network, the problem is local. If it fails on cellular too, the site itself or its DNS infrastructure may be down — in which case no amount of local troubleshooting will help, and you simply have to wait.

Also check whether you can reach sites by IP address directly. Open Chrome and navigate to http://1.1.1.1. If Cloudflare's page loads, your internet connection is intact but DNS resolution is broken. If even that fails, you have a deeper connectivity issue that goes beyond DNS.

With the steps above you should be able to resolve the error in under five minutes in the vast majority of cases. Start with the cache flush, move to changing your DNS server, and if that still fails, check your VPN and security software. Persistent cases almost always trace back to third-party software intercepting DNS traffic.