DNS Troubleshooting

How to Fix “DNS Server Not Responding” Errors

If pages won't load but your Wi-Fi shows connected, DNS is almost always the culprit. Run the lookup below to confirm, then work through the platform-specific fixes.

Confirm DNS is the actual problem

Before changing settings, isolate the issue:

Run a DNS lookup against a well-known domain (e.g. cloudflare.com). If it fails here too, your resolver is unreachable.
Try the same domain from your phone on cellular data. If it works there, the problem is on your local network.
Open a known IP directly in the browser (e.g. 1.1.1.1). If that loads, you have connectivity — only DNS is broken.

Fix it on Windows

Open Settings → Network & Internet → Advanced network settings.
Select your adapter, choose Edit DNS server assignment, switch to Manual.
Set IPv4 preferred to 1.1.1.1, alternate to 1.0.0.1.
In an admin PowerShell, run ipconfig /flushdns.

Fix it on macOS, iOS and Android

macOS: System Settings → Network → Details → DNS → add 1.1.1.1 and remove old entries.
iOS: Settings → Wi-Fi → tap (i) → Configure DNS → Manual → add 1.1.1.1.
Android: Settings → Network & internet → Private DNS → enter one.one.one.one.

If it's still broken

Power-cycle your router for a full 30 seconds. If the error returns within hours, your ISP's upstream resolver is unstable — keeping a public DNS configured permanently is the most reliable fix. Pro users can schedule a recurring DNS health check from the dashboard to catch resolver outages before they affect work.

Recommended next steps

Diagnostic workflow

1
Test DNS resolution
Confirm your resolver is unreachable, not just slow.
Run DNS lookup
2
Measure DNS speed
Compare your current resolver against public alternatives.
DNS speed test
3
Verify the destination is alive
Once DNS is fixed, confirm the target server actually responds.
Check server
4
Set up monitoring
Track resolver health so the next outage isn't a surprise.
Open dashboard

Frequently asked questions

What does 'DNS server not responding' mean?

Your device couldn't reach the DNS resolver it was configured to use, so it can't translate domain names into IP addresses. The internet is up — name resolution is broken.

Should I switch to 1.1.1.1 or 8.8.8.8?

Both are reliable public resolvers. 1.1.1.1 (Cloudflare) typically responds in under 15 ms; 8.8.8.8 (Google) is similar. Either is faster than most ISP defaults.

Why does restarting the router fix this?

Most home routers run a small DNS forwarder. When it gets wedged — by leaked memory, a stale upstream, or a bad cache entry — a power cycle clears it.

Could a VPN cause this?

Yes. VPN clients often push their own DNS server. If that resolver is down or unreachable, every lookup fails until the VPN is disconnected or its DNS is overridden.

How do I confirm DNS is really the problem?

Try opening a site by IP address. If the IP works but the domain doesn't, DNS is the issue — not your connection.