The “DNS server not responding” error means your device can reach the network but can’t translate website names into addresses — so nothing loads even though you’re “online.” It sounds technical; the fixes are simple. Here they are in order.
Fix it step by step
- Try a different browser or device. This confirms whether it’s system-wide (network problem) or just one app.
- Restart your router — unplug 30 seconds, plug back in, wait two minutes. A stalled router is the most common cause.
- Flush your DNS cache. Windows:
ipconfig /flushdnsin Command Prompt. Mac:sudo dscacheutil -flushcachein Terminal. This clears bad stored lookups. - Change your DNS server to a reliable public one: 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare). This is the fix that works most often, because the error usually means your ISP’s DNS is down or slow.
- Restart your device to clear any stuck network state.
- Temporarily disable antivirus/firewall to test — some security suites block DNS. If that’s the cause, add an exception rather than leaving it off.
How to change your DNS
| Device | Where |
|---|---|
| Windows | Network settings → Adapter → Properties → IPv4 → set DNS to 8.8.8.8 / 8.8.4.4 |
| Mac | System Settings → Network → Details → DNS → add 1.1.1.1 |
| Android | WiFi → network → IP settings → Static, or use Private DNS: dns.google |
| iPhone | WiFi → (i) → Configure DNS → Manual → add 8.8.8.8 |
Why this error happens
Every website name (like example.com) has to be converted to a numeric IP address by a DNS server before your device can connect. If that server — usually your ISP’s — is overloaded, misconfigured or down, the translation fails and you get “DNS server not responding,” even though your actual connection is fine. That’s why switching to Google’s or Cloudflare’s public DNS fixes it so reliably: you’re simply using a faster, more stable translator.
If it keeps coming back
A recurring DNS error usually means an unstable router or a flaky ISP connection. Log in at 192.168.1.1 Router Login to update the router firmware, and if the whole connection drops (not just DNS), work through WiFi Connected But No Internet instead.
What does 'DNS server not responding' mean?
Your device can reach the network but the DNS server that translates website names into addresses isn’t answering — so pages won’t load even though you appear connected.
How do I fix DNS server not responding?
Restart your router, flush the DNS cache, and switch your DNS to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare). Changing DNS resolves the majority of cases.
Is 8.8.8.8 or 1.1.1.1 better?
Both are excellent. 8.8.8.8 is Google’s; 1.1.1.1 is Cloudflare’s and markets itself as privacy-focused and very fast. Either fixes most DNS errors — pick one.
How do I flush DNS on Windows?
Open Command Prompt and run: ipconfig /flushdns. You’ll see a confirmation that the DNS Resolver Cache was cleared.
Can antivirus cause DNS server not responding?
Yes — some security suites filter DNS and can block it. Temporarily disable it to test; if that’s the cause, add an exception instead of leaving protection off.