You ran a network test — maybe macOS Wireless Diagnostics, a browser's connectivity checker, or a router app — and it came back with "DNS Server Not Responding." The confusing part: your Wi-Fi icon says you're connected. So which is it?
Here's the key distinction. "DNS server not responding" is a resolver problem, not an offline problem. Your Mac has a working network path to your router; what's failing is the step that translates a name like apple.com into a numeric IP address. That's the DNS lookup. When the DNS server (usually your router or your ISP) doesn't answer, apps and browsers hang on "looking up…" and you get this message — even though the underlying connection is fine.
That's good news, actually. It means most of the time you can fix this yourself in a couple of minutes. Work through these in order; the fastest and most common fixes are first.
The fixes, fastest first
1. Confirm it really is DNS (30 seconds)
Open Terminal (Spotlight → type "Terminal") and run:
ping -c 3 1.1.1.1
If the pings succeed (you get replies) but websites still won't load by name, that's the signature of a DNS failure — the raw connection works, only name lookups are broken. Now run:
ping -c 3 apple.com
If the first ping works and the second fails with "cannot resolve," DNS is confirmed as the culprit. Keep going.
2. Flush the DNS cache
Your Mac keeps a local cache of recent lookups. A stale or poisoned entry can cause exactly this error. Flush it in Terminal:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Enter your password (you won't see it typed — that's normal), press Return, then reload the page. This alone fixes a large share of "DNS not responding" cases.
3. Switch to a public DNS server
If your ISP's or router's DNS is the thing that's down, point your Mac at a fast, reliable public resolver instead. Go to System Settings → Wi-Fi → Details (next to your network) → DNS, then add these servers with the + button:
- 1.1.1.1 and 1.0.0.1 (Cloudflare — usually fastest)
- or 8.8.8.8 and 8.8.4.4 (Google)
Remove any old entries above them, click OK, and reload. If sites load now, your provider's DNS was the problem. We walk through this in detail — including how to make it permanent and how to revert — in how to change DNS settings on a Mac.
4. Toggle Wi-Fi off and on
Click the Wi-Fi icon, turn it Off, wait ten seconds, and turn it back On. This forces your Mac to request a fresh DHCP lease — which includes fresh DNS server addresses from the router. Simple, and it clears a surprising number of cases.
5. Renew the DHCP lease
If toggling Wi-Fi didn't take, renew the lease manually. Go to System Settings → Wi-Fi → Details → TCP/IP and click Renew DHCP Lease. This re-negotiates your IP address and the DNS servers your router hands out. Watch for a self-assigned IP (starting with 169.254) — that means DHCP itself failed, which is a deeper issue than DNS.
6. Restart the router (give it two full minutes)
The DNS resolver that's "not responding" is very often the one built into your own router. Unplug it, wait two full minutes (not ten seconds — the cache needs time to clear), then plug it back in and let it fully boot. Restart your Mac too while you're at it. If every device in the house had DNS trouble, this is usually why.
7. Check for a VPN, firewall, or content blocker
A VPN with a broken tunnel, a "DNS leak protection" setting, or a network-level ad blocker can intercept DNS and then fail to answer. Disconnect any VPN, temporarily disable third-party firewall or filtering apps, and test again. Corporate or school configuration profiles (System Settings → General → VPN & Device Management) can also force a specific DNS server — if one is set there and it's down, you'll see this error until it's removed.
8. Try a different network
Tether to your phone's hotspot for one minute. If DNS works on the hotspot but not on your home Wi-Fi, the problem is your router or ISP, not your Mac. If it also fails on the hotspot, the issue is on the Mac itself — a bad configuration profile, a corrupted network setting, or (rarely) failing hardware.
How this differs from other "no internet" errors
It's easy to mix these up. Quick map:
- "DNS server not responding" — the resolver failed. Connection is fine; name lookups aren't. (This guide.)
- "Server cannot be found" in Safari — usually the same root cause seen from the browser, but can also be a typo or a single dead site.
- "You are not connected to the Internet" (but you are) — often a captive-portal login or a clock/date problem, not DNS.
- Wi-Fi keeps dropping — intermittent connection loss rather than a steady resolver failure.
When it's the hardware, not the software
If DNS fails on every network you try, other Macs work fine on your Wi-Fi, and none of the above helps, you may be looking at a failing Wi-Fi card or logic-board issue. That's diagnosable but not always worth repairing on an older machine. If your MacBook's networking is genuinely dying, we'll still give you a real number for it as a trade-in — even with broken Wi-Fi — toward a working replacement.
Frequently Asked Questions
Why does my Mac say "DNS server not responding" when my Wi-Fi is connected?
Because Wi-Fi and DNS are two different layers. Wi-Fi connects your Mac to the router; DNS translates website names into IP addresses. You can have a perfect Wi-Fi connection while the DNS server (your router or ISP) fails to answer lookups — which is exactly what this error describes.
Is "DNS server not responding" a Mac problem or a router problem?
Most often it's the router or ISP — the DNS resolver they provide is the one that isn't responding. That's why switching to Cloudflare (1.1.1.1) or Google (8.8.8.8) DNS, or restarting the router, fixes it so often. If it fails on your phone's hotspot too, then the problem is on the Mac.
Does flushing DNS on a Mac delete anything important?
No. Flushing the DNS cache only clears temporarily stored name-to-IP lookups. Your Mac rebuilds them automatically as you browse. It's completely safe and is one of the first things to try.
What's the best DNS server to use on a Mac?
Cloudflare's 1.1.1.1 is typically the fastest and is privacy-focused; Google's 8.8.8.8 is a reliable alternative. Both are far more dependable than most default ISP resolvers. See how to change DNS on a Mac for step-by-step setup.
I fixed it but it keeps coming back. Now what?
Recurring DNS failures usually point at the router (aging, overheating, or firmware that needs updating) or a VPN/filtering app that keeps re-enabling itself. Set your Mac to a public DNS permanently, update or replace the router, and check for a configuration profile forcing a bad DNS server.