DNS Propagation
Query one record across resolvers worldwide.
Enter a value above to run DNS Propagation
e.g. example.com
Quick answer
DNS Propagation queries the same DNS record from resolvers in different locations worldwide and shows what each one returns. Matching answers everywhere mean your change has fully propagated; differing or missing answers mean some regions are still serving the old record.
DNS Propagation queries a single record type for one hostname against many public resolvers spread across different countries and networks, then shows you each answer side by side. When you change an A, CNAME, MX, or TXT record, the update does not reach the whole internet at the same moment. Caches from your previous TTL keep serving the old value until they expire. This tool lets you watch that rollout in real time, so you can confirm a change is live globally before you cut over traffic, announce a migration, or troubleshoot why some visitors still land on the old server.
How it works
You enter a hostname, pick a record type, and the tool sends the same query to a list of geographically distributed resolvers such as Google, Cloudflare, Quad9, and regional providers. Each resolver answers from its own cache or by walking to your authoritative nameservers. Because every resolver cached the previous record at a different time, their remaining TTL differs, which is exactly why one location shows the new IP while another still returns the old one.
How to read the results
Compare the value column across all locations. When every resolver returns the same up-to-date answer, propagation is effectively complete for that record. Mixed results mean some caches still hold the old value and will refresh once their TTL counts down. Timeouts or SERVFAIL usually point at an unreachable or misconfigured nameserver, not slow propagation. Remember this reflects public resolver caches, not the private DNS on any single user's device or router.
Common problems & fixes
If a change refuses to spread, first confirm it exists at the authoritative source rather than a cache. A long previous TTL is the usual cause of slow rollout, so lower TTL well before a planned migration. Check that you edited the correct zone and did not leave a stale record of the same type. If only your own machine lags, flush its local DNS cache instead of waiting on the global picture.
Frequently asked questions
- How long does DNS propagation take?
- It is bounded by the record's previous TTL. If the old value had a 3600-second TTL, caches can keep serving it for up to an hour after your edit. Registrar or nameserver changes may take longer because parent zone TTLs are often 24 to 48 hours. Lowering TTL before a change shortens the window considerably.
- Why do some locations still show the old record?
- Those resolvers cached the previous answer and their TTL has not expired yet. Each resolver picked up your old record at a different moment, so they refresh at different times. This is normal and resolves on its own. If a location stays stale far beyond the TTL, that resolver may honor a minimum cache time or ignore your published value.
- Does this reflect what my own visitors see?
- Partly. The tool samples large public resolvers, which many people use, but individual visitors may rely on their ISP resolver, a corporate DNS server, or a local cache on their router or device. Those can lag behind the public resolvers shown here. Consistent answers across these locations is a strong signal, not an absolute guarantee for every user.