If Chrome shows DNS_PROBE_FINISHED_NO_INTERNET and you are looking for dns_probe_finished_no_internet how to fix chrome, the message simply means Chrome tried to look up a website’s address and got no response from your DNS server. DNS (Domain Name System) is the internet’s phone book — it translates names like google.com into IP addresses. When that lookup fails, Chrome cannot load anything, even though your Wi-Fi icon may insist you are “connected.” The good news: this error is almost always a local configuration problem — stale DNS cache, a bad DNS server, a proxy setting, or a Chrome glitch — and the 7 fixes below resolve it in minutes.

Work through them in order. Fix 2 alone solves it for most people.

Table of Contents

• What Does DNS_PROBE_FINISHED_NO_INTERNET Mean?
• Fix 1: Restart Your Devices and Check the Connection
• Fix 2: Flush the DNS Cache and Renew Your IP
• Fix 3: Change Your DNS Server to Google DNS
• Fix 4: Disable the Proxy Server in Chrome
• Fix 5: Clear Chrome’s DNS Cache via chrome://net-internals
• Fix 6: Temporarily Disable VPN, Firewall, and Antivirus
• Fix 7: Reset Chrome Settings and Update Chrome
• Preventing the Error From Coming Back
• FAQs
• Conclusion

What Does DNS_PROBE_FINISHED_NO_INTERNET Mean?

When you type a URL into Chrome, this happens behind the scenes:

1. Chrome asks your configured DNS server: “What is the IP address of this domain?”
2. The DNS server answers with an IP address.
3. Chrome connects to that IP and loads the page.

DNS_PROBE_FINISHED_NO_INTERNET means step 1 failed — Chrome’s DNS probe finished with no usable internet path to a DNS server. Note the nuance: it does not necessarily mean your internet is down. It means Chrome could not complete a DNS lookup. The underlying causes fall into a few buckets:

• Stale or corrupt DNS cache: Your PC or Chrome cached a bad DNS response and keeps replaying it.
• Unreachable DNS server: Your router or ISP’s DNS server is down, slow, or misconfigured.
• Wrong proxy settings: A leftover or broken proxy routes Chrome’s DNS queries into a dead end.
• VPN or security software interference: VPN clients and firewalls intercept DNS traffic; if they malfunction, lookups fail.
• Router or ISP outage: Genuinely no internet — the Wi-Fi icon can show “connected” to the router while the router itself has no upstream connection.

The fastest diagnostic: open another browser (Edge, Firefox) or another app. If everything is down, the problem is your connection or router — start with Fix 1. If only Chrome fails while other apps work, jump straight to Fix 4 or Fix 5. If other Chrome errors appear too, our guide to the ERR_CONNECTION_TIMED_OUT error in Chrome covers its sibling issues.

Fix 1: Restart Your Devices and Check the Connection

Before touching settings, confirm the basics. A surprising number of DNS errors vanish after a clean restart of the network chain.

1. Check whether anything works: Try loading a site in another browser, and try a non-browser app (email, messaging). If nothing works, the issue is the connection, not Chrome.
2. Restart your router: Unplug the router’s power cable, wait a full 30 seconds, plug it back in, and wait 2 minutes for it to fully reconnect.
3. Restart your computer: A reboot clears temporary network states and the system DNS cache.
4. Test again in Chrome. If the error persists, continue to Fix 2.

If your Wi-Fi shows as connected but no app can reach the internet, your router may have lost its upstream link — check for a red or orange light on the router, and confirm other devices on the same network are also offline before continuing.

Fix 2: Flush the DNS Cache and Renew Your IP

Windows keeps a local DNS cache so repeat visits load faster. When that cache goes stale or corrupt — common after switching networks or router changes — every lookup fails until the cache is cleared. Flushing it plus renewing your IP address fixes the majority of DNS_PROBE_FINISHED_NO_INTERNET cases.

1. Press Windows key + X and select Terminal (Admin) or Command Prompt (Admin).
2. Release your current IP address:
   
   ipconfig /release
3. Flush the DNS resolver cache:
   
   ipconfig /flushdns
   
   You should see “Successfully flushed the DNS Resolver Cache.”
4. Renew your IP address:
   
   ipconfig /renew
5. Close the terminal and test Chrome.

While you are in the terminal, you can verify DNS is working with a quick test: type nslookup google.com and press Enter. If it returns IP addresses, DNS resolution is functional and Chrome should work. If it times out, the problem is your DNS server — move on to Fix 3.

Fix 3: Change Your DNS Server to Google DNS

By default, your PC uses your ISP’s DNS servers via your router. ISP DNS servers are a common failure point — they go down, get slow, or return bad responses. Switching to a public DNS provider like Google DNS (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1) bypasses the problem entirely and often speeds up browsing.

Change DNS on Windows 11

1. Open Settings > Network & internet > Wi-Fi (or Ethernet if wired) and click your connected network.
2. Under DNS server assignment, click Edit.
3. Change the dropdown from Automatic (DHCP) to Manual.
4. Toggle IPv4 on and enter:
   
   Preferred DNS: 8.8.8.8
   
   Alternate DNS: 8.8.4.4
5. Click Save, then flush the DNS cache again (ipconfig /flushdns) and test Chrome.

Change DNS on Windows 10

1. Open Control Panel > Network and Sharing Center > Change adapter settings.
2. Right-click your active connection and choose Properties.
3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
4. Choose “Use the following DNS server addresses” and enter 8.8.8.8 and 8.8.4.4.
5. Click OK on both dialogs, flush DNS, and test.

Google’s public DNS is free, fast, and reliable, which is why it is the standard recommendation in Google’s own Public DNS documentation. If you prefer an alternative, Cloudflare’s 1.1.1.1 and 1.0.0.1 work the same way. After switching, run nslookup google.com to confirm lookups succeed.

Fix 4: Disable the Proxy Server in Chrome

A misconfigured proxy server is a classic cause of DNS_PROBE_FINISHED_NO_INTERNET that only affects Chrome. Proxies are sometimes left behind by uninstalled VPN software, corporate setups, or even malware. Chrome on Windows uses the system proxy settings, so you fix them in Windows.

1. Open Settings > Network & internet > Proxy.
2. Under Automatic proxy setup, turn off “Automatically detect settings” if it is causing issues (you can re-enable it later), and make sure “Use setup script” is off.
3. Under Manual proxy setup, make sure “Use a proxy server” is turned off — unless you knowingly need a proxy for work or school.
4. Alternatively, in Chrome go to Settings > System > Open your computer’s proxy settings, which opens the same page.
5. Restart Chrome and test.

If you do need a proxy (office or school network), get the correct address, port, and any credentials from your network administrator rather than guessing. An incorrect proxy entry produces exactly this error, so double-check every character if you re-enter one manually.

Fix 5: Clear Chrome’s DNS Cache via chrome://net-internals

Chrome keeps its own internal DNS cache, separate from Windows. Even after you flush the system cache with ipconfig /flushdns, Chrome can keep serving a stale entry from its own cache. Clearing it takes seconds.

1. In Chrome’s address bar, type chrome://net-internals/#dns and press Enter.
2. Click the “Clear host cache” button.
3. Next, go to chrome://net-internals/#sockets and click “Flush socket pools”. Stale sockets can also block new connections after DNS changes.
4. Close Chrome completely (check Task Manager to make sure no Chrome processes remain) and reopen it.
5. Test the sites that were failing.

While you are at it, clear Chrome’s browsing data for good measure: press Ctrl + Shift + Delete, select All time, tick Cached images and files and Cookies and other site data, then click Clear data. A corrupt cache entry for a specific site can mimic DNS errors on that site alone.

Fix 6: Temporarily Disable VPN, Firewall, and Antivirus

VPN clients, firewalls, and antivirus suites intercept your network traffic — including DNS queries. When they malfunction after an update, or when a VPN connection drops without restoring normal routing, Chrome’s DNS probes go nowhere.

1. Disconnect your VPN completely (not just pause it — fully disconnect or quit the app) and test Chrome.
2. If you use a third-party antivirus with a firewall or “web protection” feature, temporarily disable the web shield and test. Re-enable it immediately after testing.
3. Check Windows Firewall: open Control Panel > System and Security > Windows Defender Firewall and make sure Chrome is allowed. Click “Allow an app or feature through Windows Defender Firewall” and verify Google Chrome is ticked for both Private and Public networks.
4. Test Chrome after each change so you know which one was responsible.

If the VPN turns out to be the cause, update the VPN client to the latest version — older clients are notorious for breaking DNS on Windows after system updates. Some VPNs also offer a “kill switch” that blocks all traffic when disconnected; if yours is stuck on, DNS fails exactly this way. Never leave your antivirus disabled longer than the test itself.

Fix 7: Reset Chrome Settings and Update Chrome

If everything else checks out, Chrome’s own profile or settings may be corrupt. Resetting restores defaults without deleting your bookmarks, history, or saved passwords.

1. Make sure Chrome is updated first: click the three-dot menu > Help > About Google Chrome. Chrome checks for updates automatically — relaunch if it installs one.
2. Go to Settings > Reset settings.
3. Click “Restore settings to their original defaults” and confirm.
4. Restart Chrome and test. Your extensions will be disabled by the reset — re-enable them one at a time, since a bad extension (especially ad-blockers or “privacy” extensions that meddle with DNS) can cause this error.
5. If the error still appears, try a new Chrome profile: click your profile icon > Add > continue without an account. If the new profile works, your old profile is corrupt — sign in to sync and migrate.

As a final check, test in an Incognito window (Ctrl + Shift + N). Incognito disables extensions by default. If sites load in Incognito but not in a normal window, an extension is definitely the culprit — disable them all at chrome://extensions/ and re-enable one by one.

Preventing the Error From Coming Back

• Keep a reliable DNS server set: Leaving Google DNS (8.8.8.8) or Cloudflare (1.1.1.1) configured permanently avoids ISP DNS outages.
• Update your VPN and antivirus clients regularly — outdated network drivers in these apps are a top cause of recurring DNS failures.
• Restart your router monthly. Consumer routers accumulate stale states; a periodic reboot prevents many network oddities.
• Avoid installing multiple “privacy” or ad-blocking extensions that intercept DNS — one reputable blocker is enough.
• Keep Chrome updated. Networking-stack bugs get fixed in Chrome updates, and an outdated browser is more vulnerable to DNS quirks.

FAQs

What causes DNS_PROBE_FINISHED_NO_INTERNET in Chrome?

The most common causes are a stale DNS cache (system or Chrome’s internal cache), an unreachable or misconfigured DNS server (often your ISP’s), a broken proxy setting, interference from a VPN or antivirus, or a genuine router/ISP outage. The error means Chrome’s DNS lookup probe completed without a working path to resolve domain names — not necessarily that your internet is fully down.

Is DNS_PROBE_FINISHED_NO_INTERNET a virus?

No, it is not a virus — it is a standard Chrome network error. However, malware can change your DNS or proxy settings and produce this error as a side effect. If the error appeared suddenly alongside other strange behavior (pop-ups, redirected searches), run a full scan with Windows Security or your antivirus after fixing the DNS issue, and double-check the proxy settings in Fix 4 for entries you did not add.

Why does the error happen on only one device?

Because the cause is usually local to that device: its DNS cache, its proxy settings, its VPN client, or its Chrome profile. Other devices use their own settings and are unaffected. Run ipconfig /flushdns on the affected PC, check its proxy settings, and clear Chrome’s host cache at chrome://net-internals/#dns — one of those almost always fixes a single-device case.

Should I use 8.8.8.8 as my DNS permanently?

Yes, it is safe. 8.8.8.8 and 8.8.4.4 are Google’s free public DNS servers — fast, reliable, and widely used. Alternatives like Cloudflare’s 1.1.1.1 are equally valid. The only consideration is privacy: your DNS queries go to that provider instead of your ISP. If that concerns you, pick the provider whose privacy policy you trust most; functionally they all resolve the error the same way.

What is the difference between DNS_PROBE_FINISHED_NO_INTERNET and DNS_PROBE_FINISHED_NXDOMAIN?

NO_INTERNET means Chrome could not reach any working DNS path at all — a connectivity or configuration problem on your end. NXDOMAIN means DNS worked fine, but the domain you typed does not exist — usually a typo in the URL. If you see NXDOMAIN, check your spelling; if you see NO_INTERNET, work through the fixes in this guide.

Will resetting Chrome delete my bookmarks and passwords?

No. “Restore settings to their original defaults” resets the startup page, new tab page, search engine, pinned tabs, content settings, cookies, and extensions — but it keeps your bookmarks, browsing history, and saved passwords. Your synced data is also preserved if you are signed in to your Google account. It is a safe troubleshooting step.

Conclusion

DNS_PROBE_FINISHED_NO_INTERNET looks technical, but it boils down to one thing: Chrome could not turn a website name into an address. For most people, flushing the DNS cache with ipconfig /flushdns and renewing the IP fixes it immediately; switching to Google’s 8.8.8.8 DNS handles the cases where the ISP’s servers are at fault. If only Chrome is affected, the proxy settings and Chrome’s internal host cache at chrome://net-internals are the next places to look. Work through the seven fixes in order, keep a reliable public DNS configured, and this error will rarely bother you again. And if the same troubled update left you with other Windows issues, our guides to fixing the black screen after a Windows 11 update and File Explorer crashes in Windows 11 cover the two most common ones.