What Is DNS propagation?

Publication and caching are separate

A DNS change first needs to be published by the authoritative infrastructure serving the zone. Recursive resolvers and clients may still hold earlier answers until the applicable cache rules let them refresh. This is why two tools can show different values after an edit. The phrase propagation describes the observed transition, rather than a single broadcast that updates every machine at the same moment.

TTL affects caching, but lowering it after a resolver has already cached the old answer does not retroactively shorten that stored answer's original lifetime. Negative caching can also matter when a name was previously queried before its record existed. A generic instruction to wait a fixed number of hours misses those distinctions and can delay finding a record published in the wrong DNS account.

An email setup example

A team adds a DKIM record and one checker sees it while another reports no data. Capture the exact name and type, then compare authoritative responses with the recursive results. Check spelling, duplicated domain suffixes, delegation and the relevant timing. If the authoritative server does not contain the intended record, waiting for caches to expire will not create the missing publication.

Use evidence to decide when to proceed

Keep the original and new values, change time, authoritative observations and independent lookup results together. Test the actual mail path after the expected public data is available. Seeing a DNS answer is one step; a trusted receiver verifying the resulting signature is another. Avoid treating a successful dashboard save or a single regional checker as complete proof of email readiness.

Different caches can converge at different times, so describe what was observed rather than promising universal completion. The operational objective is correct authoritative publication followed by adequate independent readback for the intended use. That is more useful than repeatedly editing the same record or resetting an arbitrary waiting timer whenever a checker disagrees.