Topic · DNS & Infrastructure
DNS propagation
DNS propagation describes the observed delay as recursive caches expire and resolvers begin using updated authoritative DNS answers.
How it works
Authoritative changes propagate through resolver refresh behavior and TTL expiry.
What can go wrong
Different recursive resolvers can show different answers temporarily. Negative caching may also delay newly created names.
What to check or do
Reduce TTL in advance when practical and verify authoritative and recursive responses.
How to investigate DNS propagation
- Signal to investigate
- A new TXT record is visible from one resolver but missing from another.
- Evidence to collect
- Compare authoritative answers with independent recursive resolvers, cache TTLs and the SOA negative-cache settings.
- Common wrong conclusion
- DNS changes do not physically propagate as a synchronized worldwide push.
How to interpret the evidence
Each resolver can retain earlier positive or negative answers until its cache expires. A wrong authoritative zone or delegation remains wrong regardless of how long you wait.
What to change and how to verify it
Verify the authoritative zone first, then distinguish cache expiry from delegation or DNSSEC faults using multiple resolvers.
Put this into practice
Run a focused check, then explore protection if your domain needs it.