What DNS problems look like on a Mac
If direct internet reachability works but website names fail to resolve, DNS may be the broken part of the connection path.
Notes & guides
Practical explanations for normal Mac users: what speed tests miss, how to separate Wi-Fi from DNS or ISP trouble, and what evidence is worth keeping when a problem comes and goes.
If direct internet reachability works but website names fail to resolve, DNS may be the broken part of the connection path.
Build a useful support record with timestamps, duration, reliability history, repeated patterns, and privacy-safe evidence instead of screenshots of one speed test.
Throughput can look excellent while short outages, latency spikes, jitter, or failed requests still make the connection frustrating.
Short outages often disappear before you can test them. The useful evidence is what happened before, during, and after the incident.
Background monitoring should stay lightweight. Heavy throughput tests belong behind explicit actions, not silent recurring checks.
A reliability score should summarize availability and stability without hiding the evidence or pretending sparse history is complete.
A fast connection can still be unreliable. Learn what speed, latency, jitter, failed checks, and outages each tell you about your internet.
Latency measures delay; jitter measures how much that delay moves around. Both can make a fast connection feel unreliable.
Onlink records the incident, captures lightweight evidence around it, and preserves uncertainty without silently launching a full speed test.
A practical connection-path model for separating local Wi-Fi trouble, router problems, DNS failures, and wider internet outages.