Windows 'DNS server isn't responding' fix that actually works

You're connected to Wi-Fi. The icon says you have internet. But when you open a browser, you get 'DNS server isn't responding' or error code 0x80072EFD. This happens most often after you switch from one network to another

Maybe you left a coffee shop and came home. Or your office VPN dropped. The network adapter gets confused. It keeps trying to use the old DNS server address. That server doesn't respond on the new network, so your PC gives up.

Here's the real root cause: your computer cached a bad or outdated DNS record. Windows holds onto it stubbornly. Even if you disconnect and reconnect, it keeps using the old entry. You need to force it to let go.

Step 1: Run the network troubleshooter (quick check, not the fix)

Open Settings, go to Network & Internet, then Status. Click 'Network troubleshooter'. It will probably say 'DNS server isn't responding'. That confirms the issue, but the troubleshooter rarely fixes it. Move on to step 2.

Step 2: Flush the DNS cache from Command Prompt

This is the main fix. It clears every stored DNS entry your PC is hoarding.

1. Press Windows key + R, type cmd, then press Ctrl+Shift+Enter to run as administrator.
2. Type ipconfig /flushdns and press Enter.
3. You should see: 'Windows IP Configuration. Successfully flushed the DNS Resolver Cache.'
4. Close the Command Prompt and try loading a website. If it still fails, go to step 3.

After flushing, Windows has to ask the network for fresh DNS info. That's what you want.

Step 3: Reset the Winsock catalog and TCP/IP stack

Sometimes the DNS resolver itself is corrupted. Resetting it fixes that.

1. Open Command Prompt as administrator again.
2. Type netsh winsock reset and press Enter. Wait for 'Successfully reset the Winsock Catalog. You must restart the computer in order to complete the reset.'
3. Type netsh int ip reset and press Enter. You'll see 'Resetting Global, OK! Resetting Interface, OK! Restart the computer to complete this action.'
4. Restart your PC.

This rebuilds your network settings from scratch. It's a heavy hammer, but it works.

Step 4: Change your DNS server manually (if steps 2 and 3 fail)

Your ISP's DNS server might be slow or misconfigured. Switch to Google Public DNS or Cloudflare. Both are free and reliable.

1. Press Windows key + R, type ncpa.cpl, press Enter. This opens Network Connections.
2. Right-click your active network adapter (Wi-Fi or Ethernet), select Properties.
3. Double-click 'Internet Protocol Version 4 (TCP/IPv4)'.
4. Select 'Use the following DNS server addresses'.
5. For Google DNS, enter: Preferred: 8.8.8.8, Alternate: 8.8.4.4. For Cloudflare, use 1.1.1.1 and 1.0.0.1.
6. Check 'Validate settings upon exit' and click OK.
7. Close the Properties window, then restart your browser.

Your PC will now use those DNS servers for all lookups. This bypasses whatever your router or ISP is doing.

Step 5: Check the real problem—your router

If none of the above works, the issue isn't your PC. It's your router. Maybe it's overloaded. Maybe its DNS forwarder is broken. Try rebooting it: unplug the power for 30 seconds, plug it back in, wait 2 minutes. Then flush DNS on your PC again (step 2).

If that fails, log into your router settings (usually 192.168.1.1 or 192.168.0.1) and change its DNS servers to the same Google or Cloudflare addresses. That fixes every device on your network.

One last thing: if you have a VPN active, disconnect it temporarily. Some VPNs hijack DNS settings and cause conflicts. If the error disappears with the VPN off, you know who's the culprit.