DNS Propagation
Compare current DNS answers across 37 configured public resolver endpoints.
How this tool works
Use these details to understand what the result measures, what it can miss, and how DNS Kit handles the query.
Data source
DNS Kit requests the selected record from 37 configured public resolver endpoints and streams each available answer to the map and list. The endpoint labels identify represented resolver services and regions; public anycast can route a query somewhere other than the labeled city.
Caching and freshness
Each public resolver manages its own cache. Results can differ until older cached answers expire, and some providers can serve stale data or apply local cache policy. DNS Kit does not force a resolver to refresh.
Privacy and retention
The hostname is sent to DNS Kit and the configured public resolvers. Aggregate API usage stores a SHA-256 hostname hash and coarse country for up to 90 days. Website analytics and session replay may capture visible inputs and returned answers.
How to interpret the result
Matching answers show agreement among the endpoints that responded during this run. A different answer usually indicates a cached older value, provider-specific behavior or inconsistent authoritative data; inspect the TTL and authoritative zone before concluding that a resolver is wrong.
Worked example
If 34 endpoints return the new address and three return the old one, the result shows sampled disagreement at that moment. Recheck after the old record’s TTL window and confirm the authoritative answer.
Limitations
- An endpoint can time out or fail, so a run may contain fewer than 37 completed answers.
- The endpoints are public resolver services, not independent physical probes in every mapped city.
- Agreement among sampled resolvers does not prove that every network worldwide has the same answer.
Frequently asked questions
- What is DNS propagation?
- DNS propagation describes the period when recursive resolvers may return different answers after a DNS change. Each resolver refreshes its cached answer when the relevant TTL expires.
- How long does DNS propagation take?
- It depends on the previous record's TTL, resolver cache state, and the delegation path. Many changes become visible within minutes or hours, but there is no universal completion time for every resolver.
- Why do different servers show different results?
- DNS servers cache records for a period defined by the TTL. Until the cache expires, they serve the old records. Different servers may have cached records at different times, causing temporary inconsistencies.
- How can I speed up DNS propagation?
- You can lower your TTL values before making changes, flush your local DNS cache, and use services with lower TTL defaults. However, you cannot force other DNS servers to update faster.
- What does 'Empty' status mean?
- An 'Empty' status means the DNS server responded but found no records of that type for the domain. This could be normal (e.g., no AAAA record if the domain doesn't support IPv6) or indicate the change hasn't propagated yet.