How to fix the "DNS server not responding" error?
The "DNS server not responding" error means your computer sent DNS queries to its configured DNS server but got no reply, so it can't turn website names into IP addresses. To fix it, restart your router and computer, then test whether a public resolver such as 1.1.1.1 answers when your normal one doesn't. If it does, switch your DNS settings to a public resolver. If nothing answers, check for a firewall, antivirus or VPN blocking DNS traffic, disable unused network adapters, update your network driver, and reset the network stack. The problem is almost always on your device or local network, not with the websites you're trying to visit.
On Windows, you'll usually see this message from the network troubleshooter: "Your computer appears to be correctly configured, but the device or resource (DNS server) is not responding." Mac and Linux users see similar symptoms without the friendly wording. This guide explains what's actually failing, how to pinpoint the broken link with a few quick tests, and the fixes for each operating system, in the order most likely to help.
What the Error Actually Means
Every time you visit a website, your device asks a DNS server (also called a resolver) for the site's IP address. Normally that server is your home router, which forwards the question to your ISP's resolver. Sometimes it's a public resolver, a VPN's resolver, or a company DNS server.
"Not responding" is different from other DNS errors:
| Situation | What happens | Typical message |
|---|---|---|
| DNS server doesn't reply | Queries time out | DNS server not responding, DNS request timed out |
| DNS server says the name doesn't exist | NXDOMAIN answer | DNS_PROBE_FINISHED_NXDOMAIN, server can't find |
| DNS server can't get a valid answer | SERVFAIL answer | Server failed, SERVFAIL |
With a timeout, the problem is reaching the DNS server at all. That narrows the cause to your device's settings, your local network, the router, your ISP, or something blocking the traffic in between.
Step 1: Quick Checks
Before working through settings, rule out the obvious:
- Is it every website? If one site fails and others work, it's not this error. It's that site's DNS.
- Is it every device? If your phone on the same Wi-Fi also can't load anything, the router or ISP is the likely culprit. If only one computer is affected, focus on that computer.
- Do you have a connection at all? Test with an IP address that doesn't need DNS:
ping 1.1.1.1
If ping 1.1.1.1 works but websites don't load, your internet connection is fine and the problem is DNS. If ping fails too, you have a wider connectivity problem, such as a dead connection or a disconnected cable, and DNS is a symptom rather than the cause.
Step 2: Test Your DNS Server Directly
Find out which DNS server you're using and whether it answers.
On Windows
Show your configured DNS servers:
Get-DnsClientServerAddress -AddressFamily IPv4 | Where-Object ServerAddresses
InterfaceAlias Interface Address ServerAddresses
Index Family
-------------- --------- ------- ---------------
Wi-Fi 12 IPv4 {192.168.1.1}
Then query that server and a public one:
Resolve-DnsName example.com -Server 192.168.1.1 -DnsOnly
Resolve-DnsName example.com -Server 1.1.1.1 -DnsOnly
On macOS
scutil --dns | grep nameserver
nslookup example.com 192.168.1.1
nslookup example.com 1.1.1.1
On Linux
On distributions using systemd-resolved, resolvectl status shows the real upstream servers for each interface:
resolvectl status
dig @192.168.1.1 example.com +short
dig @1.1.1.1 example.com +short
A timeout looks like this:
;; communications error to 192.168.1.1#53: timed out
;; no servers could be reached
Interpreting the Results
- Your normal DNS server times out, 1.1.1.1 answers: Your router or ISP resolver is the problem. Restart the router (Step 3) and, if needed, change your DNS server (Step 4).
- Both time out: Something on your computer or network is blocking DNS entirely. Check firewalls, VPNs and adapters (Steps 5 to 8).
- Both answer: DNS works from the command line, so the issue is likely a stale cache, a browser setting, or an intermittent fault. Flush the cache and restart.
Step 3: Restart Your Router and Computer
It sounds too simple, but this fixes a large share of cases. Many home routers run a small DNS forwarder that can hang, run out of memory, or lose its connection to the ISP's resolvers while the internet connection itself stays up.
- Unplug the router (and modem, if separate) from power.
- Wait about 30 seconds.
- Plug the modem in first, wait for it to come online, then the router.
- Restart your computer.
If DNS works again for a while and then fails repeatedly, the router's DNS forwarder is unreliable. Changing your device's DNS server to a public resolver avoids it entirely.
Step 4: Change Your DNS Server
Using a well-run public resolver is a fast fix and often improves reliability:
| Provider | Primary | Secondary |
|---|---|---|
| Cloudflare | 1.1.1.1 | 1.0.0.1 |
| Google Public DNS | 8.8.8.8 | 8.8.4.4 |
| Quad9 | 9.9.9.9 | 149.112.112.112 |
Always configure two servers, ideally from the same provider, so one can take over if the other is unreachable.
Windows
Through the GUI, go to Settings > Network & internet, select your connection, then find DNS server assignment and click Edit. Switch to Manual, turn on IPv4, and enter the addresses.
In PowerShell as administrator:
# Find the adapter name
Get-NetAdapter | Where-Object Status -eq "Up"
# Set DNS servers
Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ServerAddresses ("1.1.1.1","1.0.0.1")
# Revert to automatic (DHCP) later if needed
Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ResetServerAddresses
macOS
Through the GUI, open System Settings > Network, choose your connection, click Details, then DNS, and add the servers with the + button.
In Terminal:
networksetup -listallnetworkservices
sudo networksetup -setdnsservers Wi-Fi 1.1.1.1 1.0.0.1
# Revert to automatic later
sudo networksetup -setdnsservers Wi-Fi empty
Linux
With NetworkManager:
nmcli connection show
sudo nmcli connection modify "Home WiFi" ipv4.dns "1.1.1.1 1.0.0.1" ipv4.ignore-auto-dns yes
sudo nmcli connection up "Home WiFi"
On a server using systemd-resolved directly, set global servers in /etc/systemd/resolved.conf:
[Resolve]
DNS=1.1.1.1 1.0.0.1
FallbackDNS=9.9.9.9
Then restart the service:
sudo systemctl restart systemd-resolved
resolvectl status
On the Router
To fix every device at once, change the DNS servers in your router's WAN or DHCP settings. The exact menu varies by brand. Look for "DNS server" under the internet or LAN settings, replace the ISP-provided addresses, save, and reconnect your devices.
Step 5: Check Firewalls, Antivirus and Security Software
DNS normally uses UDP port 53, with TCP port 53 for larger responses. A firewall rule or security product that blocks this traffic produces exactly this error.
- Third-party antivirus or internet security suites: Some include "web protection" that intercepts DNS. Temporarily disable it and test.
- Windows Defender Firewall: Default rules allow outbound DNS, but custom rules or a corporate policy may not. Check outbound rules for anything blocking port 53.
- Linux firewalls: A restrictive outbound policy in UFW, firewalld or nftables can block DNS.
On Linux with UFW, outbound DNS needs to be allowed if the default outgoing policy is deny:
sudo ufw status verbose
sudo ufw allow out 53/udp
sudo ufw allow out 53/tcp
Some networks, particularly corporate and public Wi-Fi, block DNS to any server except their own. If your normal DNS works but public resolvers time out on such a network, that's deliberate. Use the network's own DNS server while you're connected to it.
Step 6: Disconnect VPNs and Check Proxy Settings
VPN clients usually replace your DNS servers with their own. If the VPN tunnel drops but the DNS setting stays, every lookup goes to a server you can no longer reach.
- Disconnect the VPN completely, or quit the app.
- Test DNS again.
- If it now works, reconnect and check whether the problem returns. If it does, contact the VPN provider or try a different server location.
Also check that no unexpected proxy is set. On Windows, go to Settings > Network & internet > Proxy. On macOS, go to System Settings > Network > Details > Proxies.
Step 7: Disable Unused Network Adapters
Windows can try to send DNS queries over adapters that aren't connected properly, such as an old VPN adapter, a virtual machine adapter, or a second network card. This can cause intermittent timeouts.
List all adapters in PowerShell:
Get-NetAdapter | Format-Table Name, InterfaceDescription, Status
Disable any you don't need (you can enable them again later):
Disable-NetAdapter -Name "Ethernet 3" -Confirm:$false
Step 8: Reset the Network Stack
Windows
If settings look correct but DNS still fails, resetting Windows networking components often clears the problem. Run Command Prompt as administrator:
ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock reset
netsh int ip reset
Restart the computer afterwards. Note that netsh int ip reset clears manual IP settings, so if you use a static IP address, note it down first.
Also make sure the DNS Client service is running:
Get-Service -Name Dnscache
It should show Running. This service is managed by Windows and can't normally be stopped by users. If it isn't running, a system file check may help:
sfc /scannow
macOS
Flush the DNS cache and renew your DHCP lease:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
sudo ipconfig set en0 DHCP
Replace en0 with your interface name, which you can find with networksetup -listallhardwareports. If problems persist, removing and re-adding the network service in System Settings > Network gives you a fresh configuration.
Linux
Restart the resolver and network services:
sudo systemctl restart systemd-resolved
sudo systemctl restart NetworkManager
Also check that /etc/resolv.conf points somewhere sensible. On systemd-resolved systems it should be a symlink to the stub file:
ls -l /etc/resolv.conf
cat /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Oct 2 09:12 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
nameserver 127.0.0.53
options edns0 trust-ad
search .
If the file has been overwritten with a server that no longer exists, recreate the symlink:
sudo ln -sf ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
Step 9: Update or Reinstall the Network Driver
A buggy or corrupted network driver can cause packets, including DNS queries, to be dropped. On Windows:
- Open Device Manager.
- Expand Network adapters.
- Right-click your Wi-Fi or Ethernet adapter and choose Update driver.
- If that doesn't help, choose Uninstall device, then restart. Windows reinstalls the driver automatically.
You can also download the latest driver from your laptop or motherboard manufacturer's website, which is often newer than the one Windows Update offers.
Step 10: Test IPv6 Separately
Sometimes the IPv6 path is broken while IPv4 works. Your device might be trying an IPv6 DNS server first and waiting for it to time out. Test both:
dig @1.1.1.1 example.com +short
dig @2606:4700:4700::1111 example.com +short
If the IPv6 query times out while IPv4 works, check the IPv6 settings on your router. As a temporary workaround, you can set IPv4 DNS servers manually as shown in Step 4, or disable IPv6 on the affected adapter. Fixing the router's IPv6 configuration is the better long-term solution.
Step 11: Contact Your ISP
If every device on your network times out on DNS, public resolvers also fail, and a router restart doesn't help, your ISP may be having an outage or filtering DNS traffic. Check the ISP's status page or social media, and contact support with the results of your tests. Being able to say "ping to 1.1.1.1 works but DNS queries to it time out" gets you past the first-line script much faster.
FAQ: DNS Server Not Responding
The most common causes are a router whose DNS forwarder has stopped working, an ISP resolver outage, a VPN that changed your DNS settings, security software blocking DNS traffic, or incorrect DNS server addresses on your device.
Yes. Cloudflare, Google and Quad9 run large, reliable public resolvers with published privacy policies. Changing DNS only affects how names are looked up, not your internet connection itself, and you can switch back at any time.
Recurring timeouts usually point to an unreliable router, a flaky Wi-Fi connection, or a VPN that keeps dropping. Setting public DNS servers on your device or router avoids an unreliable router forwarder, and updating the router's firmware can help too.
Yes. Some security suites intercept DNS traffic to filter websites. If that component fails, DNS stops working. Temporarily disabling the web protection feature is a quick way to test this.
On its own, rarely, because the problem is that the server isn't answering at all. Flushing helps once the server is reachable again, by clearing any failed or stale entries left in the cache.
Connect a computer directly to the modem, or query a public resolver from your computer. If public resolvers answer but the router doesn't, the router is the problem. If nothing answers, including public resolvers, the ISP connection is more likely at fault.
Conclusion
"DNS server not responding" means your device can't get any reply from its DNS server. The quickest way through it is to test: ping an IP address to confirm you have a connection, then query your normal DNS server and a public one. That tells you straight away whether to restart the router and change DNS servers, or to look at firewalls, VPNs and network settings on your computer.
For most people, a router restart followed by switching to a reliable public resolver solves it for good. If it doesn't, work through security software, unused adapters, a network stack reset and driver updates. If every device on your network is affected and public resolvers are unreachable too, it's time to contact your ISP.
