DNS Propagation Checker
Check whether a DNS record has propagated across major public resolvers.
| Resolver | Status | Answers |
|---|
About the DNS Propagation Checker
DNS propagation is the time it takes for a DNS change to become visible everywhere on the internet, since every resolver caches records independently until their TTL expires. This causes the common situation where a change looks correct from your own computer but a friend on a different network still sees the old value. This tool queries several major public resolvers at once so you can see exactly how far a change has spread, rather than guessing or repeatedly refreshing a single lookup.
How it works
DNSbyte queries the same record for your domain against multiple independent public DNS resolvers simultaneously, each one operated by a different provider with its own cache. If every resolver agrees, the change has fully propagated. If results differ between resolvers, some are still serving a cached value from before the change and have not yet refreshed.
Resolvers checked:
- Google's public DNS resolver, widely used by default on Android devices.
- Cloudflare
- Cloudflare's 1.1.1.1 resolver, known for fast response times.
- Quad9
- A security-focused resolver that also blocks known malicious domains.
- Mullvad
- A privacy-focused resolver that does not log queries.
Frequently asked questions
Why do different resolvers show different results for the same record?
Each resolver caches DNS records independently based on the TTL set on that record. If you changed a record recently, resolvers that already had the old value cached will keep serving it until that cached copy expires, while resolvers that have not seen the record yet will fetch the new value immediately.
How long should I expect propagation to fully complete?
It depends entirely on the TTL that was set on the record before you changed it, not the new TTL. A record with a one hour TTL will generally be fully updated everywhere within about an hour of the change, while a 24 hour TTL means some resolvers may still serve the old value for up to a day.
All resolvers show the new value except one, is that resolver broken?
Not necessarily, it may simply have an older cached copy with more time left before expiry, or it may have queried your name servers at a slightly different moment during the transition. Recheck after the original TTL period has fully elapsed.
Can I speed up propagation by lowering the TTL after I have already changed a record?
No, lowering the TTL on the new record only affects how long the new value will be cached going forward, it has no effect on resolvers that already cached the previous record under the old, longer TTL. To make future changes propagate faster, lower the TTL in advance of the next change, not after.
Why does my own computer show the new record immediately but DNSbyte shows it still propagating?
Your computer or local network may be using a resolver that has not cached the record yet, or you may have cleared your own local DNS cache, while other public resolvers around the world are still serving their previously cached copy. Both states can be correct at the same time.