DNS server not responding
Your device sent DNS questions to its configured DNS server and got no answer. Names can't be turned into addresses, so websites and apps can't connect.
Quick checks
- Restart the router and modem: unplug for 30 seconds, then plug back in.
- Check other devices on the same network. If they fail too, the router or ISP is the problem.
- Try mobile data or another Wi-Fi network to rule out your device.
- Disconnect any VPN and try again.
Fixes on Mac
1. Switch to a public DNS server
- Open System Settings › Network, choose Wi-Fi or Ethernet and click Details.
- Select DNS, add
1.1.1.1and8.8.8.8, remove the router's address, and click OK.
2. Flush the DNS cache
- In Terminal, run
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
- In Terminal, run
3. Renew the DHCP lease
- System Settings › Network › Wi-Fi › Details › TCP/IP › Renew DHCP Lease.
4. Check which DNS servers macOS uses
- Run
scutil --dns | grep nameserverin Terminal. - If you see addresses you don't recognise, a VPN, profile or app has set them. Remove it or reset the setting.
- Run
5. Test whether DNS or the connection is down
- Run
ping -c 3 1.1.1.1. Replies mean the internet works and only DNS is failing. - Run
dig example.com @1.1.1.1. If that answers butdig example.comdoesn't, your configured DNS server is the problem.
- Run
Fixes on Windows
6. Flush DNS and reset Winsock
- In an administrator Command Prompt, run
ipconfig /flushdns,netsh winsock resetandnetsh int ip reset. - Restart the PC.
- In an administrator Command Prompt, run
7. Set DNS servers manually
- Settings › Network & internet › your connection › Hardware properties › DNS server assignment › Edit › Manual.
- Enter
1.1.1.1and8.8.8.8for IPv4.
8. Update or reinstall the network driver
- In Device Manager › Network adapters, right-click your adapter › Update driver, or uninstall it and restart.
Other devices
9. Fix it on the router for every device
- Log in to the router (often
192.168.1.1or192.168.0.1). - Find the DNS or WAN settings and replace the ISP's DNS with
1.1.1.1and8.8.8.8. - Update the router's firmware if an update is available.
- Log in to the router (often
Still not working?
If every device fails and ping 1.1.1.1 also gets no reply, the problem isn't DNS: your internet connection is down. Check the modem's lights and your ISP's status page.
If only DNS fails and changing to a public DNS server doesn't help, something may be intercepting port 53: some routers, security software and ISPs do. Try encrypted DNS (DNS over HTTPS), which goes over port 443.
See what’s happening
When DNS is down, apps keep retrying. LightAtom's connections view shows which apps are trying to connect and whether any connection gets through.
Frequently asked questions
What does “DNS server not responding” mean?
Your device's DNS server, usually your router or your ISP's resolver, isn't answering requests to translate names into addresses. Without that, browsers and apps can't find servers.
How do I fix DNS server not responding on a Mac?
Restart the router, then set 1.1.1.1 and 8.8.8.8 in System Settings › Network › Details › DNS, and flush the cache with sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
Is changing my DNS server safe?
Yes. Public resolvers from Cloudflare, Google and Quad9 are reliable and often faster than ISP servers. You can switch back by removing them in network settings.
Why does it keep happening?
An overloaded or failing router is the most common cause, especially older ISP-supplied ones. Setting public DNS on the router and updating its firmware often stops it.
Can a VPN cause DNS server not responding?
Yes. A VPN replaces your DNS servers with its own; if the tunnel drops or its resolver fails, lookups stop. Reconnect or switch VPN servers.