Network

DNS is not working on your Mac. Pages fail while the connection looks fine.

By the Noah team·Updated September 2, 2026·6 min read
Short answerYour Mac has to look up the address a website lives at before it can load anything. That lookup is called DNS. When it fails you get the confusing case: Wi-Fi says connected, but pages do not open and the error mentions a server that cannot be found. One test separates it from a real outage — if a numeric address answers and a name does not, the connection works and only the lookup is broken.

The Wi-Fi menu says you are connected. Messages might still arrive. But the browser sits there and eventually reports that it cannot find the server.

That combination usually means one specific thing, and it is worth proving before changing any settings.

First, prove it really is DNS

Nearly every wasted hour here comes from skipping this. Reach an address made of numbers, then reach one made of words. A numeric address needs no lookup, so it tests the connection on its own.

zsh — Terminal
% ping -c 3 1.1.1.1
Sample result
3 packets transmitted, 3 packets received, 0.0% packet loss

Replies mean the connection itself is working. No replies means this is not a DNS problem — the network is down.

zsh — Terminal
% ping -c 3 apple.com
Sample result
ping: cannot resolve apple.com: Unknown host

The number answered and the name did not. That is DNS failing, and the rest of this page applies.

If both fail, stop here — the connection is the problem, not the lookup.

Check which servers your Mac is actually asking

Pages fail everywhere, in every browser, on this Mac only.

Your Mac normally takes its DNS servers from the router. The settings screen shows what you typed; it does not always show what is in effect, because a VPN or network app can override it.

zsh — Terminal
% scutil --dns | head -20
Sample result
resolver #1
  nameserver[0] : 192.168.1.1
  if_index : 14 (en0)

The nameserver lines are the servers being asked right now. An address you do not recognise usually belongs to network software.

Fixif the listed server is the router and nothing else on the network can browse either, the router's own lookup service is the suspect — restart it before changing anything on the Mac.

Clear the saved answers

One site fails while others load, or a site started failing right after it moved or changed host.

Your Mac remembers recent lookups for a while so pages open faster. If an answer was saved while something was broken, or a site has since moved, the saved answer keeps being used.

zsh — Terminal
% sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Asks for your password and prints nothing when it works. Silence is success here.

Fixclear the saved answers, then reload the failing page. If it works, a stale answer was the cause and nothing further is needed.

Rule out a VPN or content filter

The failure started after installing a VPN, a security tool, or parental controls — or after one of those was removed.

These work by handling your lookups for you. When they are uninstalled carelessly, or disconnect without cleaning up, the Mac can keep sending lookups to a server that is no longer answering.

This is the case where the settings screen is least trustworthy, which is why the resolver check above matters more than what any preference pane displays.

What Noah can determine on this Mac

NoahNoah can run the numeric-versus-name test for you. It reads the resolvers actually in effect rather than the ones configured, which is how a resolver belonging to network software gives itself away. It then tells you whether the failure is on this Mac or upstream at the router. That split decides whether changing anything here can help.

Noah will not silently repoint your Mac at a different DNS provider. Changing where your lookups go is a real change to how the machine reaches the internet, so it is proposed with the reason and applied only with your approval.

The short version

  • A number answers and a name does not: DNS is the problem.
  • Neither answers: the connection is the problem, and this page does not apply.
  • Read the resolvers in effect, not the ones in the settings screen.
  • Clear the saved answers before changing any configuration.
  • If every device on the network fails the same way, fix the router, not the Mac.
Try Noah free

Websites that load again.

Just tell Noah what's wrong:

DNS is not working on my Mac — websites will not load.
Find why lookups are failingFirst conversation free7-day free trial afterOnly with your OK

Already have Noah? Open it on this problem →

Frequently asked questions

Why does my Mac say it is connected to Wi-Fi but no websites load?

Being connected only means the Mac reached the network. It still has to look up each website's address. When that lookup fails, the connection indicator stays healthy while pages do not open.

How do I know it is DNS and not my internet?

Reach a numeric address such as 1.1.1.1, then a name such as apple.com. If the number answers and the name does not, the connection works and only the lookup is broken.

Does flushing the DNS cache delete anything?

No. It clears recently saved lookups so your Mac asks again. Nothing personal is removed and no settings change.

Should I change my DNS servers to a public one?

It often works, but it is a real change to how your Mac reaches the internet and it can mask a router fault rather than fix it. Prove where the failure is first.

Keep readingConnected to Wi-Fi but nothing loads →Wi-Fi that keeps disconnecting →Find the real reason your Mac is slow →

Commands in this guide are standard, read-only macOS diagnostics unless noted; anything that changes your system is called out. When in doubt, back up first with Time Machine.