Glossary · DNS
DNS Resolver: definition, explanation, and why it matters
A server that handles DNS lookups on behalf of a client — walking the global DNS hierarchy and returning the IP address for a queried domain.
Definition
A server that handles DNS lookups on behalf of a client — walking the global DNS hierarchy and returning the IP address for a queried domain.
Plain-English explanation
Your device almost never queries authoritative DNS servers directly. Instead, it asks a resolver — typically your ISP's, a public one, or one provided by your router — which performs the recursive lookup and caches the answer.
Resolver performance has an outsized impact on perceived web responsiveness because every new domain requires a lookup before connections begin.
Real-world examples
- Cloudflare's 1.1.1.1 is a public resolver. Your home router often runs a small forwarding resolver that delegates to its upstream.
Why it matters
Switching resolvers is the easiest performance and reliability tweak in networking. Many problems disappear instantly when a slow ISP resolver is replaced.
Common misconceptions
- Myth: All resolvers return the same answers.
Reality: Filtering resolvers can block or redirect domains. CDN-aware resolvers may also return different IPs to optimize routing.
Frequently asked questions
- Resolver vs DNS server — what's the difference?
- 'DNS server' is generic — it could be authoritative (owns records) or recursive (answers queries by walking the hierarchy). A 'resolver' is specifically the recursive kind.