How slow is too slow for DNS?
A DNS answer from a nearby or cached resolver usually takes under 50 ms; an uncached lookup can take 100–300 ms. Over half a second is slow, and over a second or two users notice, because every new site waits for DNS before it can connect.
What it looks like in the packets
- The time between a DNS query and its response is large.
- The connection to that site starts only after the answer arrives, so the delay adds to page load time.
- Later lookups of the same name are fast once cached.
Common causes
- An overloaded or distant resolver.
- Packet loss forcing retries.
- Slow authoritative name servers for that domain.
- A VPN sending DNS through a far-away tunnel.
What to check
- Compare lookup times for several names: one slow name or all of them?
- Try a different resolver and compare.
- Look for retried queries, which mean loss rather than slowness.
Wireshark display filters
dns.time > 0.5
How Blame Finder flags it
Warning when the slowest answer for a name takes 1.5 seconds or more; Low above 500 ms. Upload a capture and the finding links straight to the packets behind it, with the most likely culprit at the top.