What is DNS propagation?

DNS propagation refers to the period after a DNS change when different resolvers may still return different answers.

In reality, there is no global "propagation" event. What people observe is the effect of caching and TTL behaviour across different resolvers.

Recursive resolvers cache DNS responses for the duration defined by the TTL (Time To Live).

If one resolver cached the old answer before the change and another queries after the change, they will return different results until the cache expires.

; Before change
example.com. 300 IN A 1.1.1.1

; After change
example.com. 300 IN A 2.2.2.2

Resolvers that cached 1.1.1.1 will continue to return it until the TTL expires, even though the authoritative answer is already 2.2.2.2.

TTL determines how long a resolver will cache a DNS response before querying again.

Lower TTL values reduce the time caches hold old data, while higher TTLs increase cache duration.

; Low TTL (faster changes)
example.com. 60 IN A 2.2.2.2

; High TTL (slower changes)
example.com. 86400 IN A 2.2.2.2

Because of this, TTL planning is important before making DNS changes.

• The exact record type that was changed (A, CNAME, MX, etc.)
• Whether different public resolvers return different answers
• Whether the authoritative nameserver returns the expected value
• Whether TTL values explain the timing of observed differences
• Whether intermediate caching (e.g. browser or OS) may be involved

# Query different public resolvers
dig @8.8.8.8 example.com
dig @1.1.1.1 example.com

# Query authoritative server directly
dig @ns1.example.com example.com

# Check TTL remaining
dig example.com

The authoritative nameserver always has the current source of truth.

Resolvers may return cached data that is no longer current, depending on TTL.

; Authoritative answer
example.com. 300 IN A 2.2.2.2

; Cached resolver answer
example.com. 120 IN A 1.1.1.1

In this example, the resolver still returns the old IP with 120 seconds remaining in cache.

DNS propagation is often described as a fixed delay, such as "it takes 24 hours."

In reality, different resolvers refresh at different times depending on when they last cached the record and what TTL was set.

This means propagation is best understood as a cache visibility issue rather than a global update process.

• Lower TTL before planned DNS changes to reduce cache duration
• Verify the authoritative answer first before checking public resolvers
• Test against multiple resolvers to understand cache spread
• Allow time for caches to expire rather than repeatedly changing records

If you want to validate this topic in practice, these DNS Pro tools are the fastest next step.

• DNS Propagation Checker
• Record Lookup
• Domain DNS Summary