1. DNS Server Isn't Responding (The Real Problem 90% of the Time)
You're connected to your WiFi. The little bars are full. But Chrome says DNS_PROBE_FINISHED_NO_INTERNET, and nothing loads. I've seen this hundreds of times on Windows 11, Windows 10, iPhones, and Android phones. The trigger is usually your ISP's DNS server going down for a few minutes, or your router's DNS cache getting stuck.
Here's the fix that works for 9 out of 10 people. You're going to switch your computer or phone to use Google's public DNS — 8.8.8.8 and 8.8.4.4. It's free, it's faster than most ISPs, and it never goes down for more than seconds.
On Windows 11 and Windows 10
- Press Windows + R, type
ncpa.cpl, and hit Enter. You'll see your network adapters. - Right-click the adapter you're using — it'll say Wi-Fi or Ethernet. Select Properties.
- Find Internet Protocol Version 4 (TCP/IPv4) in the list. Double-click it.
- In the window that pops up, select Use the following DNS server addresses.
- Type
8.8.8.8for Preferred DNS server and8.8.4.4for Alternate DNS server. - Click OK, then close all windows.
- Open Command Prompt as admin: press Windows + X, select Terminal (Admin).
- Type
ipconfig /flushdnsand press Enter. You'll see Successfully flushed the DNS Resolver Cache. - Then type
ipconfig /renewand press Enter. Wait 20 seconds.
After that, open a browser. You should see pages load. If they don't, try one more thing before moving on: restart the browser completely. Sometimes it's holding onto the bad DNS.
On iPhone or iPad
- Go to Settings > Wi-Fi.
- Tap the blue (i) next to your connected network.
- Scroll down to Configure DNS. Tap it, then switch from Automatic to Manual.
- Tap Add Server and type
8.8.8.8. Then add another:8.8.4.4. - Remove any existing servers by tapping the red minus.
- Tap Save in the top right.
- Turn WiFi off and back on from Control Center.
Now test. If you still can't load anything, the problem isn't DNS — move to the next fix.
2. Your IP Address Is Duplicated or Stale
Another common cause: your device got an IP address that's already in use on the network, or the DHCP lease expired and your router handed out a bad one. This happens when you move between different WiFi networks a lot, or when your router's been running for months without a reboot. You'll see an error like IP configuration is invalid or No IP address.
Real-world scenario: you were at Starbucks, connected to their guest WiFi, then came home, and your laptop didn't realize it should ask for a new IP from your home router. It's still holding the Starbucks IP, which doesn't work on your home network.
Release and Renew Your IP Address
- Open Command Prompt as admin (same way as before).
- Type
ipconfig /releaseand press Enter. Your connection will drop. That's normal. - Wait 10 seconds. Then type
ipconfig /renewand press Enter. This asks the router for a fresh IP. - Wait up to 30 seconds. You'll see a new IP address appear.
- Type
ipconfig /flushdnsjust to be safe, then press Enter. - Close Command Prompt and try browsing.
If that didn't work, the next step is to reset your network stack. This fixes deeper driver-level issues.
Reset Network Stack on Windows 11
- Open Command Prompt as admin again.
- Type these commands one at a time, pressing Enter after each:
netsh int ip reset
netsh winsock reset
- You'll see Resetting Winsock cache... success. Close everything.
- Reboot your computer. This is important — these commands don't fully take effect until reboot.
- After reboot, connect to WiFi again. Should work now.
3. The Router Needs a Real Power Cycle (Not Just a Reset Button)
This is the one everyone jumps to first, but I'm putting it third because it's often a waste of time if the DNS or IP was the real issue. However, sometimes the router itself has a stuck DHCP table or a corrupted routing table. The fix is a proper power cycle, not just pressing the reset button on the back.
The trigger: your router has been on for weeks. You've got multiple phones, laptops, smart TVs, and IoT devices connected. The router's memory gets fragmented, and it stops handing out valid routes to the internet.
How to Power Cycle a Router (The Right Way)
- Unplug the power cable from the router. Not just turn it off with a switch — actually pull the plug.
- If you have a separate modem (like a cable modem from Comcast or a fiber ONT from AT&T), unplug that too.
- Wait full 60 seconds. I count to 60. Thirty seconds isn't enough. The internal capacitors need to fully discharge.
- Plug the modem back in first. Wait until all its lights are solid (usually 1-2 minutes).
- Plug the router back in. Wait until its WiFi light is steady.
- On your computer, forget the WiFi network and reconnect. This forces a fresh DHCP request.
If you still can't browse after this, it's probably an ISP outage. Call them. But 95% of the time, one of these three things fixes it.
Quick-Reference Summary Table
| Cause | Symptom | Fix | Time to Try |
|---|---|---|---|
| DNS server down | DNS_PROBE_FINISHED_NO_INTERNET, pages won't load |
Set DNS to 8.8.8.8 / 8.8.4.4 | 3 min |
| Stale or duplicate IP | No IP address error, connection drops | ipconfig /release and /renew | 2 min |
| Router memory full | Everything connected but nothing loads | Full power cycle (60 sec unplug) | 5 min |