What the Message Means
Every device needs a DNS resolver to turn names into IP addresses. Usually this is your router, which forwards questions to your internet provider. “DNS server not responding” means your device sent DNS questions and got no answer. Your connection may still be up; only name lookups fail. A quick test: if you can reach a site by IP address but not by name, DNS is the problem.
Fixes in Order
1. Restart the Router and Modem
Switch them off for 30 seconds. This fixes a surprising share of DNS problems because the router’s own DNS forwarder can hang.
2. Try Another Device or Network
If other devices on the same Wi-Fi also fail, the router or provider is the issue. If only one computer fails, focus on that computer.
3. Flush DNS and Renew the Address
ipconfig /flushdns
ipconfig /release
ipconfig /renewRun these in an administrator Command Prompt on Windows.
4. Use a Public DNS Server
Set the network adapter’s DNS servers manually, for example to 1.1.1.1 and 8.8.8.8. If that fixes the problem, your provider’s resolver was failing. Our guide to public DNS servers compares the options and shows the settings.
5. Check VPN, Firewall and Security Software
Security suites and VPN clients install network filters. A broken filter can block DNS. Temporarily disable them, or reinstall the software.
6. Reset the Network Stack
netsh winsock reset
netsh int ip resetRestart the computer afterwards. On Windows 10 and 11, “Network reset” in Settings does the same and reinstalls network adapters.
7. Update the Network Driver
Outdated or faulty Wi-Fi and Ethernet drivers occasionally cause intermittent DNS failures.
If Only Some Sites Fail
When most sites work but a few do not, the problem is probably not your resolver. Check the failing domain with our DNS Record Lookup and Is My Site Down. A domain that does not resolve anywhere has its own DNS problem; see DNS_PROBE_FINISHED_NXDOMAIN.
For Network Administrators
- Check that the internal DNS server is running and reachable on UDP and TCP port 53.
- Check that its forwarders or root hints work.
- Check DHCP: clients must receive the correct DNS server addresses.