DNS_PROBE_FINISHED_NO_INTERNET in Chrome: how to fix it

Published Sources checked By helps.wiki editorial team

DNS_PROBE_FINISHED_NO_INTERNET means Chrome could not look up the site's address through DNS, even though your device may show as connected. Start by rebooting the router and testing another device, then clear the DNS cache and switch to a different DNS server.

Applies to:Google ChromeNot tied to a specific versionMicrosoft Edge, Brave and other Chromium browsersWindows 10 and Windows 11macOSFlush command only
On this page

What it means

Before a browser can open a website, it has to turn the site name into a numeric address. That job belongs to DNS. When the lookup fails, Chrome shows DNS_PROBE_FINISHED_NO_INTERNET. In practice it means the browser can't resolve the name or can't reach DNS at all, even though your Wi-Fi or Ethernet icon may say you are connected.

This is not the same as DNS_PROBE_FINISHED_NXDOMAIN. With NXDOMAIN, a DNS server did answer and said the name does not exist. Here, the lookup never got a usable answer. Google does not document this particular error code, so the explanation and fixes below come from general DNS and connection troubleshooting, not from a Chrome-specific page.

Work through the steps in order. The first few take a minute and fix a large share of cases.

Symptoms and causes

You are likely dealing with this problem if:

  • Chrome shows "This site can't be reached" with DNS_PROBE_FINISHED_NO_INTERNET
  • Wi-Fi or Ethernet looks connected
  • Sometimes only Chrome is affected, sometimes every app, sometimes only one device on the network

The usual causes, most common first:

Connection down or faulty router/modem
The link to the internet is actually broken, or the router or modem is misbehaving, even though the device shows as connected.
Unreachable DNS server
The default DNS server handed out by your ISP or router is not responding.
Stale or corrupt DNS cache
Windows or Chrome is holding on to bad lookup results.
Antivirus or firewall interference
Third-party security software can block Chrome or DNS traffic.
Damaged network stack or driver
A corrupt TCP/IP stack, Winsock catalog or network adapter driver.
Problem on the website's side
If only one site fails, on every network and device, its DNS records may be misconfigured or still propagating.
VPN, proxy, extensions or a captive portal
Any of these can interfere with the connection. Public Wi-Fi may also need you to sign in first.

How to fix it

Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.

1.Find out how wide the problem is

Easy

Tells you whether to fix the browser, the PC or the network, so you do not change settings you do not need to.

  1. Open the same site in another browser, then on another device (a phone on the same Wi-Fi works), then try a different site.
  2. Check the address for typos.
  3. Turn the router and modem off, wait a short while, then turn them on and give them a few minutes to reconnect.
  4. On public Wi-Fi, open an http:// page (not https://) and sign in to the network's portal if it appears.

2.Test in Incognito, then update Chrome

Easy

If the page loads in Incognito, an extension is the likely culprit. An outdated browser or OS can also cause connection errors.

  1. Open an Incognito window with CtrlShiftN and load the site.
  2. If it works, turn off extensions one at a time in Chrome's extensions page until the error stops, and leave the offending one disabled.
  3. Update Chrome and restart it. Install any pending operating system updates too.

3.Run the Windows network troubleshooters

Easy

Windows can sometimes detect and repair a broken adapter or connection setting on its own.

  1. Open Settings and find the Troubleshoot settings. The exact menu path differs between Windows versions.
  2. Run Internet Connections, Incoming Connections and Network Adapter in turn and apply any fix they offer.

4.Clear Chrome's host cache

Easy

Chrome keeps its own DNS cache, separate from Windows. A bad entry there can keep the error alive.

  1. Type this address into Chrome's address bar and press Enter:
    Text
    chrome://net-internals/#dns
  2. Click Clear host cache, then close and reopen Chrome.

5.Flush the DNS cache and renew your IP address

Easy

Microsoft documents /flushdns as discarding the DNS resolver cache, including negative entries (remembered failures). Release and renew request a fresh address from the router.

Before you start: /release turns off TCP/IP on adapters that get their address automatically until you run /renew, so run both lines together. These two only affect adapters set to obtain an address automatically.

  1. Open Command Prompt as administrator and run the three commands one after another.
    Command Promptrun as administrator
    ipconfig /flushdns
ipconfig /release
ipconfig /renew
  2. Reload the page in Chrome.

6.Rule out antivirus or firewall software

EasyChanges settings

Third-party security software sometimes blocks Chrome or DNS requests.

Before you start: Only pause a third-party antivirus or firewall briefly, for testing. Turn it back on straight away afterwards. Do not leave protection off.

  1. Pause your third-party antivirus or firewall and reload the page.
  2. Turn the protection back on immediately, whatever the result.
  3. If the page loaded while it was paused, add an exception for Chrome in that program's settings.

7.Switch to a different DNS server

Moderate

If the DNS server from your ISP or router is failing, a public one can restore lookups.

  1. Open Network Connections (for example, press WinR, type ncpa.cpl and press Enter).
  2. Right-click your active adapter, choose Properties, select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  3. Choose Use the following DNS server addresses and enter Google Public DNS: preferred 8.8.8.8, alternate 8.8.4.4.
  4. Click OK, restart the PC and test again. To undo it later, switch the setting back to Obtain DNS server address automatically.

8.Reset Winsock and the TCP/IP stack

ModerateChanges settings

Repairs a corrupt network stack, which can break lookups even when the connection itself is fine.

Before you start: This resets network settings. If you use a custom static IP configuration, write it down first so you can enter it again afterwards.

  1. Open Command Prompt as administrator and run both commands.
    Command Promptrun as administrator
    netsh winsock reset
netsh int ip reset
  2. Restart the computer and test Chrome again.

9.Update the network adapter driver

Moderate

An outdated or damaged adapter driver can cause intermittent connection problems.

  1. Open Device Manager, expand Network adapters, right-click your adapter and choose Update driver.
  2. If Windows finds nothing, download the driver from the PC or adapter manufacturer's own website.

10.Clear browsing data, then reset Chrome

ModerateChanges settings

A last browser-side step if the error appears only in Chrome and the earlier fixes did nothing.

Before you start: Resetting Chrome disables your extensions. Bookmarks and saved passwords are kept.

  1. Press CtrlShiftDel, set the time range to All time and clear the data.
  2. If the error remains, open chrome://settings/reset and reset the settings to their defaults.

11.On a Mac: flush the DNS cache

Easy

The macOS equivalent of clearing the resolver cache.

  1. Open Terminal and run the command below, entering your Mac password when asked. This is the commonly cited command for recent macOS versions.
    Terminal
    sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

12.If you run the website that fails

Advanced

When only one domain fails for everyone, the cause is likely its DNS setup, not your visitors' devices.

  1. Check that the domain's DNS records are correct and have finished propagating.
  2. If the problem persists after about 48 hours, contact your registrar.
  3. Lower the TTL before you change records, so updates spread faster.

Check that it worked

  • The site that failed now opens in Chrome without the error page.
  • Other sites also load, and the result is the same after restarting Chrome.

If it still fails

  • If every device and browser on your network fails, the fault is with the router, modem or ISP. Check the router's status lights and contact your internet provider.
  • If only one site fails on every network and device, the problem is probably on the site's side. Try again later or contact the site's owner.
  • If only one PC is affected after the steps above, note which step changed anything and check your VPN or proxy settings and your security software's logs.
  • See Google's Fix connection and loading errors in Chrome for the general troubleshooting list.

Questions

How is this different from DNS_PROBE_FINISHED_NXDOMAIN?

NXDOMAIN means a DNS server replied that the name does not exist. NO_INTERNET means Chrome could not get a usable answer from DNS at all. See the NXDOMAIN article for that case.

Does it only happen in Chrome?

No. It appears in Chromium-based browsers such as Edge and Brave. Sometimes every app is affected, sometimes only one device on the network.

Sources

  1. How to Fix "DNS_probe_finished_no_internet" in Google Chrome · HelpDeskGeek
  2. DNS Byte: how to fix DNS probe finished no internet · DigiCert
  3. Fix connection and loading errors in ChromeOfficial · Google Chrome Help
  4. ipconfigOfficial · Microsoft Learn

Browse