DNS Server Not Responding: How to Fix the Error on Windows, Mac and Routers
The DNS server not responding error means a device could not receive a usable reply from its configured DNS resolver. Wi-Fi or Ethernet may still appear connected while websites fail because names cannot be translated into IP addresses.
The problem may be local to one device, caused by a router or VPN, related to an ISP resolver, or caused by the authoritative DNS of one domain.
Check the affected domain from multiple DNS locations.
How to Diagnose the DNS Error
Begin by separating internet connectivity from name resolution. If an IP address is reachable but a domain lookup fails, DNS is a likely cause. If every device fails, investigate the router or ISP before changing each computer.
Step-by-Step Process
- Try another website and another device.
- Restart the browser, computer, modem and router.
- Temporarily disconnect VPN or proxy software.
- Flush the local DNS cache.
- Renew the device IP configuration.
- Test a known public resolver.
- Check the affected domain from an external DNS checker.
Important Concepts
Windows commands
Use ipconfig /flushdns, ipconfig /release, ipconfig /renew and network reset commands as needed.
Router DNS relay
A failed router relay can affect every device on the network.
VPN DNS
A VPN may force queries to an internal resolver that becomes unreachable.
Security filtering
Firewalls and endpoint-security software may intercept or block DNS traffic.
Common Problems and Mistakes
- Incorrect manually entered DNS address
- ISP resolver outage
- Router firmware or DNS relay failure
- VPN split-DNS problem
- Firewall blocking DNS traffic
- Broken authoritative DNS for one domain
Troubleshooting Checklist
- Test another device.
- Test another network.
- Run nslookup against the default resolver.
- Run nslookup against 1.1.1.1 or 8.8.8.8.
- Check the domain globally.
- Return DNS to automatic if manual values are wrong.
Frequently Asked Questions
Why is Wi-Fi connected but no websites open?
The local wireless connection can work while DNS or the upstream internet connection fails.
Will changing DNS fix every problem?
No. It will not repair an expired domain, broken authoritative DNS, DNSSEC errors or a failed web server.
Is restarting the router useful?
Yes. It can renew the WAN connection and clear a failed DNS relay, although it is not a guaranteed fix.
Conclusion
DNS Server Not Responding is an important topic for anyone managing websites, networks or online services. Use the diagnostic steps above to separate local-device, resolver, authoritative DNS and application problems.