DNS Probe Finished No Internet Windows 11 Fix

Chrome cannot translate a site name into an IP address. Start by checking whether the problem appears in one site, all sites, or only after sleep, because that pattern points to different fixes. If the error appears everywhere, move straight to Windows network commands instead of spending time on browser-only cleanup.

Quick answer

The issue can come from Chrome itself, Windows networking, or the router and ISP path after a connection drop, VPN change, or DNS server failure.

Is it a browser problem or a Wi‑Fi problem?

The symptom pattern tells you where to start. If Chrome fails but other browsers load the same site, treat it as a Chrome cache or socket issue first. If every browser fails, treat it as a Windows, adapter, gateway, or DNS-server problem instead.

If the PC shows Wi‑Fi connected but pages still do not load, focus on the adapter, gateway, and DHCP lease. A common first-timer mistake is changing DNS servers before checking whether the device even has a valid IPv4 lease.

DNS fix matrix

Likely causes

Most often, the problem is a bad or unreachable DNS server, a local DNS cache that still points Chrome to the wrong place, or a stale DHCP lease. Other possibilities include a broken adapter setting, a corrupted Winsock or TCP/IP stack, VPN or proxy interference, or a router setting that is handing out the wrong DNS server.

Chrome-only failure

If Chrome is the only browser that fails, clean Chrome’s own DNS state before touching Windows settings. That keeps you from making system-wide changes for a browser-local problem.

1. In Chrome, open chrome://net-internals/#dns if your version still supports that page.
2. Select Clear host cache.
3. Close Chrome completely, then reopen it and retry the site.
4. If the page still fails only in Chrome, test the same site in another browser before changing adapter or router settings.

All browsers fail

If every browser fails, move to the Windows network stack. The first command clears stale name lookups; the next two refresh the lease if DHCP has gone stale.

1. Open Command Prompt or Windows Terminal as administrator.
2. Run ipconfig /flushdns.
3. If the device recently lost its connection, run ipconfig /release, then ipconfig /renew.
4. If the problem remains, run netsh winsock reset and netsh int ip reset.
5. Reboot Windows 11 after the reset commands.

Suppose a laptop wakes from sleep and shows Wi‑Fi connected, but every site times out in Chrome and Edge. That points away from a single browser and toward a stale lease or stack issue, so the release/renew sequence belongs before public DNS changes.

Wi‑Fi connected but no internet

This pattern usually points to the adapter, gateway, or DHCP, not the browser. Check the active network first, because a broken lease can make public DNS changes useless.

1. Open Settings > Network & internet > Wi‑Fi or Ethernet.
2. Select the active connection and open Hardware properties.
3. Verify that the device has an IPv4 address, gateway, and DNS server listed in ipconfig /all.
4. Open Windows Terminal (Admin) and run ipconfig /release, then ipconfig /renew.
5. If the lease does not recover, use netsh winsock reset and netsh int ip reset, then restart.

DNS works on one device but not another

If a phone or second PC reaches the same sites, the network path is probably fine and the problem sits on the Windows 11 device. Compare adapter DNS settings, proxy, and VPN state before changing the router.

1. Open Settings > Network & internet > Wi‑Fi or Ethernet, then open Hardware properties.
2. Check whether DNS is set manually on the affected device.
3. Temporarily turn off VPN and Proxy in Settings > Network & internet > VPN and Proxy.
4. Run ipconfig /all in Command Prompt to compare DNS and adapter details.
5. Check whether the Windows DNS Client service is running if the lookup problem persists.

What command fixes it on Windows 11?

The most useful command sequence is ipconfig /flushdns first, then ipconfig /release and ipconfig /renew if the DHCP lease looks stale. If the problem stays after that, reset Winsock and the TCP/IP stack, then restart Windows 11.

Run the commands from an elevated prompt, not a normal one. The stack reset commands typically require a reboot before they can take effect.

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

Should you change DNS servers first?

Change DNS servers first when the error affects all browsers, or when another device on the same network works while this Windows 11 PC does not. If only Chrome fails, clear Chrome’s cache first; changing adapter DNS before that is usually the wrong branch.

1. Go to Settings > Network & internet > Wi‑Fi or Ethernet.
2. Open the active adapter, then select Hardware properties and DNS server assignment.
3. Set a manual IPv4 DNS option.
4. Enter 8.8.8.8 and 8.8.4.4 for Google Public DNS, or 1.1.1.1 and 1.0.0.1 for Cloudflare DNS.
5. Save the change, then retry the site and compare results.

Use public DNS as a test and a fix, not a blanket cure. If the site starts loading after the switch, the DNS server from the router or ISP was likely the weak point.

If that didn’t work, try this next

1. Run ping 8.8.8.8 from Command Prompt to check basic connectivity.
2. Run nslookup example.com 8.8.8.8 to compare DNS answers against a public resolver.
3. Review ipconfig /all and look for the active DNS server, gateway, and adapter status.
4. If VPN or proxy is enabled, turn both off and retest before blaming the ISP.
5. If the issue appears on every device, check the router’s DNS settings or contact the ISP.

Say your desktop loads local network pages but cannot open public sites until you change DNS from the automatic setting to 1.1.1.1. That points to upstream DNS resolution, not a broken browser. If the same change helps one PC but not another, the affected device likely has a local adapter or proxy setting to fix next.

Still not working?

If none of the earlier steps help, move to the more invasive fixes: Settings > Network & internet > Advanced network settings > Network reset, or a driver reset from Device Manager > Network adapters. Use network reset only when the adapter or stack looks corrupted, because it removes saved network settings and forces Windows to rebuild them.

Check proxy, VPN, and adapter properties again before calling the issue a provider problem. If every device on the network fails and public DNS does not help, the router DNS is the next place to inspect.

Prevention: after a VPN session, keep an eye on whether Chrome starts failing again. If it does, clear Chrome’s host cache and flush DNS before reconnecting the VPN or saving any manual DNS override.

Frequently asked questions

Why does DNS_PROBE_FINISHED_NO_INTERNET happen on Windows 11?

It usually appears after a connection drop, a DNS server failure, a stale DHCP lease, or a VPN that rewrote DNS settings. Windows 11 can also show it when the adapter has a bad gateway, when the Winsock stack is damaged, or when Chrome keeps a stale host entry.

Is DNS_PROBE_FINISHED_NO_INTERNET a browser problem or a Wi‑Fi problem?

Either one. If only Chrome fails, the issue is likely browser-local and starts with Chrome cache cleanup. If Edge and Firefox fail too, treat it as a Windows or network problem and use ipconfig /flushdns, then lease renewal and DNS server checks on the active adapter.

What command fixes DNS_PROBE_FINISHED_NO_INTERNET on Windows 11?

The most useful command is ipconfig /flushdns. If the connection is stale, follow it with ipconfig /release and ipconfig /renew. For a deeper repair, run netsh winsock reset and netsh int ip reset, then restart Windows 11.

Should I flush DNS or change DNS servers first?

Flush DNS first when Chrome or all browsers started failing after a connection change. Change DNS servers first when another device works on the same network or when public DNS resolves the site but your current DNS does not. Use 8.8.8.8 and 8.8.4.4, or 1.1.1.1 and 1.0.0.1.

How do I reset Winsock and TCP/IP for this error?

Open Windows Terminal (Admin) and run netsh winsock reset, then netsh int ip reset. Reboot the PC afterward. If the issue remains, go to Settings > Network & internet > Advanced network settings > Network reset for a broader rebuild of the network configuration.

What DNS server should I set on Windows 11 to fix this error?

Use Google Public DNS or Cloudflare DNS as a test on the active adapter. Google uses 8.8.8.8 and 8.8.4.4. Cloudflare uses 1.1.1.1 and 1.0.0.1. If either pair fixes the site, the router or ISP DNS path is the likely weak point.