Topic · DNS & Infrastructure
DNS resolver
A DNS resolver is a component that retrieves domain records, often by using cached answers and querying authoritative servers.
How it works
Recursive resolvers perform or coordinate the DNS lookup process required by browsers and mail infrastructure.
What can go wrong
Resolver caching can make an email-authentication change appear inconsistent between locations.
What to check or do
Compare authoritative DNS answers with multiple recursive resolvers when troubleshooting propagation.
How to investigate DNS resolver
- Signal to investigate
- An application reports DNS failure while direct authoritative queries succeed.
- Evidence to collect
- Inspect recursive resolver SERVFAIL/NXDOMAIN answers, DNSSEC validation behavior, outbound connectivity and cache state.
- Common wrong conclusion
- A recursive resolver is not necessarily the authoritative source for the domain.
How to interpret the evidence
Resolvers can cache data, validate DNSSEC and choose upstream routes differently. Discrepancies need hop-by-hop tracing rather than assuming the DNS record is incorrect.
What to change and how to verify it
Test with several independent validating resolvers, inspect authoritative records and avoid disabling DNSSEC as a shortcut.
Put this into practice
Run a focused check, then explore protection if your domain needs it.