DNS Server Isn’t Responding Fix for Windows 10 and 11
To fix the DNS server isn’t responding error, check four points in order: browser, PC, router, then ISP. The first failure tells you where the fault is. If you change settings before that, you can waste time and break a connection that was already working. This article shows the exact checks and fixes for Windows 10 and 11, with the fastest branch for each result.
What the error means
The DNS server isn’t responding error means your device cannot turn a site name into an IP address, or the lookup timed out before it finished. Start with the browser and the current network path, because that tells you whether you are dealing with one app, one PC, the router, or the ISP.
Why the page name matters more than the IP address
DNS stands for Domain Name System. It turns alphanumeric domain names into numeric IP addresses, so a browser can reach the right server. If that lookup fails, the site name stalls even when the cable or Wi-Fi icon still looks normal.
Say your laptop opens a bank site on mobile data but fails on home Wi-Fi. That split points away from the laptop screen itself and toward the home network path. Suppose one browser fails while another opens the same page immediately; the browser or extension layer is the better place to check first.
DNS triage matrix
Use this table before you touch DNS settings. It separates single-device, browser-only, router-level, and ISP-level failures, which saves time and stops you from changing working settings.
| Symptom pattern | Likely cause | Fastest verification step | Safest fix |
|---|---|---|---|
| One device only | Corrupted cache, adapter issue, VPN, or local security software | Open the same site on another device on the same Wi-Fi | Flush DNS, disable VPN, then check the adapter |
| All devices on Wi-Fi | Router state or ISP DNS problem | Test a phone on the same Wi-Fi | Restart the router, then try public DNS resolvers |
| Browser only | Browser cache, extension, or browser-specific proxy setting | Open the site in another browser | Clear that browser’s cache or disable extensions |
| VPN on | VPN DNS override or tunnel conflict | Disconnect the VPN and reload the page | Leave the VPN off while troubleshooting |
| After sleep or Windows Update | Broken adapter state or driver conflict | Reconnect after a full restart | Restart the PC, then update the network adapter driver |
| Only one website | Site outage, bad cached record, or a site-specific block | Try another known-good site | Flush DNS and wait for the site to recover |
| Ethernet works, Wi-Fi fails | Wi-Fi adapter, SSID, or router wireless setting | Switch the same PC to Ethernet | Forget and rejoin Wi-Fi, then check the Wi-Fi adapter |
| Works on mobile data but not home Wi-Fi | Home router, ISP DNS, or modem path | Compare the result on a second home device | Restart the router and test public DNS resolvers |
Is the problem only on one device?
If one device fails and others on the same network work, the fault is usually local. That makes the Windows network stack, adapter state, VPN, or security software the first place to check, not the router or ISP.
- Open the same site on another device connected to the same Wi-Fi.
- On the problem PC, switch between Wi-Fi and Ethernet if both are available.
- On Windows 11, open the system tray network icon, then run the Network troubleshooter.
- In Settings > Network & internet > Advanced network settings, note whether a VPN, virtual adapter, or unused Ethernet adapter is active.
- If the troubleshooter reports a DNS or connection issue, keep that result and move to cache and adapter checks next.
Windows 11’s Network troubleshooter is worth running early because it can flag connection or DNS problems without changing settings. If it points to a disabled adapter, a captive portal, or a failed network path, that narrows the next step fast.
Can you fix the cache?
If the error stays on one PC, a stale DNS cache is a common next stop. The safest sequence is to flush the cache, restart the browser, then test the same site again before changing DNS servers.
- Open Command Prompt with administrator rights.
- Run:
ipconfig /flushdns - Close the browser completely and reopen it.
- Reload the same site that failed.
- If needed, restart the PC and try again after the reboot.
ipconfig /flushdns
Use the flush command after a corrupted or stale DNS cache is suspected. It needs an administrator Command Prompt. If the same site starts loading after the flush, the cache was the likely bottleneck; if not, keep moving through the decision path.
Is the router or ISP at fault?
If multiple devices on the same Wi-Fi fail, the issue is more likely at the router or ISP level. Restart the router first, because it is the quickest safe reset, then compare results on a second device before you change DNS servers.
- Power off the modem and router.
- Wait 30 seconds.
- Power on the modem first, then the router.
- Reconnect one device and test the same site.
- If the failure is still on every device, try public DNS resolvers on the router or on one Windows PC.
Public DNS resolvers give you a clean comparison point. Google DNS uses 8.8.8.8 and 8.8.4.4. Cloudflare DNS uses 1.1.1.1 and 1.0.0.1. If public DNS works while the ISP-provided DNS fails, the router or ISP DNS path is the stronger suspect.
Try public DNS on Windows
On the affected PC, open Settings > Network & internet > Wi-Fi or Ethernet > Hardware properties or the adapter’s DNS settings, then enter a public resolver pair. Test one pair at a time so you can tell which change fixed the lookup.
Google DNS: 8.8.8.8 and 8.8.4.4 Cloudflare DNS: 1.1.1.1 and 1.0.0.1
Could VPN or security software block DNS?
VPNs, secondary network adapters, firewall rules, and antivirus filters can override or block DNS traffic. That is common when the browser says the server cannot be reached, but only while the VPN is connected or a security suite is active.
- Turn off the VPN completely.
- Disable secondary adapters you do not need in Settings > Network & internet > Advanced network settings.
- Temporarily pause firewall or antivirus web filtering, then retest the site.
- Open Device Manager > Network adapters and check whether the active adapter shows a warning icon.
- If the adapter looks broken or outdated, update it through Device Manager or the vendor’s software.
Firewall or antivirus software can sometimes block DNS traffic on UDP or TCP port 53. If disabling protection briefly makes the site load, restore the protection and add a narrower exception or update the security software instead of leaving it off.
If that didn’t work, try this next
If the problem still follows the same path after the steps above, move to a deeper repair. The next safe escalation is a network reset or adapter reinstall, because those fix broken Winsock or adapter state without guessing at the cause.
- Go to Settings > Network & internet > Advanced network settings > Network reset.
- Use the reset only after you have confirmed the failure is not browser-only or one-site-only.
- If the adapter still misbehaves, open Device Manager > Network adapters > (adapter) > Uninstall device, then scan for hardware changes.
- If the issue began after sleep or a Windows Update, also check the vendor’s driver package for a newer network adapter driver.
ipconfig /release ipconfig /flushdns ipconfig /renew netsh winsock reset netsh int ip reset
A common first-timer mistake is changing DNS servers before proving the error appears on more than one browser or more than one device. That can hide the real fault and make later checks harder to interpret.
Keep the network adapter driver current and leave VPN adapters off when you do routine connectivity checks. If the problem returns after sleep, the driver or adapter state deserves attention before you touch DNS again.
Frequently asked questions
How do I tell if DNS is the real problem?
Test one known-good site, then test a second device on the same network. If both devices fail on Wi-Fi but work on mobile data, DNS or the router path is likely involved. If only one browser fails, the browser or extension layer is the better target.
Should I flush DNS or change DNS servers first?
Flush first if the problem affects one PC and one browser works elsewhere. If every device on the same Wi-Fi fails, restart the router first, then try Google DNS 8.8.8.8 and 8.8.4.4 or Cloudflare DNS 1.1.1.1 and 1.0.0.1.
Is the problem my router or my DNS server?
If all devices on your home Wi-Fi fail, power-cycle the router and modem before changing anything else. If a mobile hotspot works but the home network does not, and public DNS fixes the issue, the router or ISP DNS path is the stronger suspect.
How do I fix the DNS server isn’t responding on Windows 10?
Use the same sequence as on Windows 11: run the network troubleshooter, flush the cache with ipconfig /flushdns, restart the router, then test public DNS. Windows 10 may place the adapter settings in a slightly different menu, but the commands stay the same.
How do I fix the DNS server isn’t responding error?
Start with browser-only testing, then check another device, then the router. If the failure is local, flush the cache and disable VPN or extra adapters. If it is network-wide, restart the router and test public DNS before moving to driver or network reset steps.
How to fix the DNS server isn’t responding on PS5
For a PS5, the same decision path still helps: test another device on the same Wi-Fi, restart the router, then try a manual DNS entry such as Google DNS or Cloudflare DNS in the console’s network settings. If only the console fails, the local network path is still the place to check first.
