Topic · DNS & Infrastructure

DNS negative caching

DNS negative caching lets resolvers temporarily remember that a DNS name or record type does not exist.

Email Security Glossary·Practical guidance
Share this definition LinkedIn X WhatsApp Email
01 / How it works

How it works

Resolvers use DNS authority data and negative caching limits to avoid repeated queries for missing records.

02 / What can go wrong

What can go wrong

A newly added DKIM or DMARC record may appear absent to resolvers that cached an earlier negative answer.

03 / What to check or do

What to check or do

Allow for negative-cache expiry and compare authoritative answers against affected recursive resolvers.

Practical diagnosis

How to investigate DNS negative caching

Signal to investigate
A newly created verification record stays NXDOMAIN at some locations after the authoritative zone is correct.
Evidence to collect
Query authoritative servers directly, then observe recursive responses and the SOA-derived negative-cache lifetime.
Common wrong conclusion
Repeatedly editing the working TXT record may not clear a resolver’s cached NXDOMAIN.

How to interpret the evidence

Negative responses can be cached according to DNS rules. A resolver that has cached nonexistence may continue reporting failure until expiry even after the owner name is created.

What to change and how to verify it

Check both authoritative and recursive paths, allow for negative caching, and avoid swapping provider settings repeatedly during the observation window.

Illustrative diagnostic — substitute your authorized domain or host
dig @1.1.1.1 TXT _dmarc.example.com
Educational example; not validated against your live infrastructure.
NEXT STEP

Put this into practice

Run a focused check, then explore protection if your domain needs it.

Authoritative reference ↗