What DNS problems look like on a Mac

DNS is easy to overlook because it sits between “I have a network connection” and “this website opens.”

When DNS fails, the internet can feel completely broken even though the underlying connection still reaches the outside world.

DNS translates names into addresses

Apps normally connect using names such as example.com. A DNS resolver turns that name into an address the network can use.

If that lookup fails, browsers and apps may report that a server cannot be found even when direct IP connectivity still works.

That distinction is the key clue.

A DNS failure is not the same as being offline

Consider the connection path:

Wi-Fi → Router → Website lookup → Internet

If Wi-Fi is usable and the router responds, your Mac has a local network path.

If a DNS-independent internet check also succeeds, the wider internet path may be working.

If normal name resolution fails in the middle, DNS becomes the likely problem.

Onlink’s diagnosis logic uses that kind of separation rather than treating every failed website load as a total outage.

Symptoms can be inconsistent

DNS problems are not always absolute. One name may already be cached while another needs a fresh lookup. A resolver may fail temporarily and recover. A VPN may supply a different DNS configuration from your normal network.

That can produce symptoms such as:

• some websites opening while new ones fail;
• apps recovering after a network change;
• failures that vanish after reconnecting Wi-Fi;
• a browser error that looks different from a timeout.

Those symptoms are clues, not proof.

Check the path before changing settings

Changing DNS servers is a common troubleshooting step, but it should follow evidence.

If the local gateway is not reachable, DNS is probably not the first problem to fix. If the entire internet path is down, swapping resolvers may accomplish nothing.

A manual diagnosis that checks the local gateway, DNS, direct internet reachability, and HTTPS in sequence gives you a better basis for changing configuration.

See Is the problem Wi-Fi, your router, DNS, or your ISP? for the broader model.

Intermittent DNS trouble needs history

A manual check performed after recovery may show normal DNS.

When Onlink captures automatic incident evidence, DNS status can be preserved alongside other during-incident checks. If the internet path was reachable but website lookup failed, the incident can retain that evidence after the connection recovers.

That is more useful than trying to recreate a short failure later.

Be careful with certainty

DNS is one layer in a larger system. Captive portals, VPNs, security software, and upstream failures can create similar symptoms.

A good diagnostic result should say likely DNS issue when the evidence supports it, not “your DNS provider is definitely broken.”

That is the broader principle behind intermittent incident diagnosis: preserve what the Mac observed, then make the narrowest conclusion the evidence justifies.

DNS stops being mysterious once you treat name lookup as its own stage instead of equating it with the whole internet.