MSK · UTC+3 · 18 Nov 2026note

← back

Resolver timeouts: what to check first

dns27 Oct 2026 · 3 min read

“Everything is slow” is usually “DNS is slow”. Before changing resolvers, find out which step is timing out — the query, the connection, or the answer.

Measure the resolution, not the browser

dig +stats example.com @127.0.0.53
dig +tcp example.com @127.0.0.53
dig +dnssec example.com @1.1.1.1

Compare UDP and TCP answers. UDP working while TCP times out points at a firewall that drops 53/tcp; both failing points at the resolver itself or the network in front of it.

The three usual causes

Fix the timeout, then the cache

A short timeout masks a broken resolver for months: the first query fails, the retry succeeds, and users call it “a bit slow”. Set a realistic timeout (2–3 s), enable a local cache, and watch the SERVFAIL rate. If the rate is non-zero, you have a bug, not a performance problem.