What DNS propagation actually means
When you update a DNS record—for example, point your website to a new server—the change is published at your authoritative nameserver. Other DNS resolvers may still have an earlier answer cached. People often call the period when different resolvers return different data “DNS propagation.” It is not a single update that moves across the internet at a fixed speed.
Why two visitors may see different addresses
A visitor typically uses a recursive DNS resolver selected by their internet provider, device, or network settings. If that resolver cached the previous A or AAAA record, it may return the old value until the relevant cache entry expires. A visitor using another resolver could see the updated address immediately.
The role of TTL
Time To Live (TTL) tells caching resolvers how long to retain an answer under ordinary conditions. If an old record had a TTL of 3600 seconds, a resolver that cached it shortly before a change may keep serving it for nearly an hour. Changing TTL only after migration cannot instantly clear the previous cached value.
How to check a migration
- Confirm the authoritative DNS configuration at your provider.
- Record the new expected A, AAAA, CNAME or MX value.
- Compare multiple recursive resolvers with our DNS propagation comparison.
- Account for the old TTL and for DNSSEC or delegation problems when answers remain inconsistent.
Our tool compares two well-known DNS resolver services, Google Public DNS and Cloudflare. These are independent resolver viewpoints, but they are not representative samples from every country or network.
When the record does not change
Check that the domain is delegated to the nameservers you actually edited. If the registrar points to a different DNS provider, changes to the wrong zone will never take effect. An incorrectly configured DNSSEC chain can also cause SERVFAIL even when an authoritative record exists.
Further reading: Google Public DNS documentation and Cloudflare DNS fundamentals.
Editorial note: This is general educational information, not a live audit. DNS behavior and provider policies can change, and results should be verified against authoritative sources.