DNS Propagation

DNS Propagation checks how a domain's records resolve from multiple geographic locations around the world at the same time, giving you a real-time map of whether a DNS change has spread to global resolvers. When you update a record at your DNS host, the new value does not appear everywhere instantly; each recursive resolver caches the old answer until its TTL expires. This tool queries vantage points in different regions so you can see, side by side, which locations have picked up the new record and which are still serving the previous one.

Propagation is fundamentally about caching and TTL behavior rather than data physically traveling across the network. The authoritative nameservers are updated almost immediately when you save a change, but intermediate resolvers honor the TTL that was attached to the old record before refreshing. By comparing answers from many resolvers, you get a practical sense of how far through that cache-expiry cycle a change has progressed, which is far more useful than checking a single local resolver.

The most common use case is confirming a migration: pointing a domain at a new host, switching nameservers, or updating an A record during a server move. Teams also use it before flipping production traffic, to verify that a record is consistent worldwide before announcing a launch, and to reassure stakeholders that an apparent outage is just incomplete propagation rather than a misconfiguration.

A good habit is to lower your record's TTL well before a planned change so that the propagation window is short, then raise it again once the new value is stable everywhere. If most locations show the new record but a few lag, that is normal and usually resolves within the old TTL window. For a deeper look at exactly which record values an individual resolver returns, combine this with a standard DNS Lookup.