Verify that your DNS changes have propagated to global resolvers. Compare results from Cloudflare (1.1.1.1), Google (8.8.8.8) and Quad9 (9.9.9.9) in one click.
DNS propagation time depends on the TTL (Time to Live) value of the previous record. If your old A record had a TTL of 3600 seconds (1 hour), resolvers worldwide may continue serving the old IP for up to one hour after you make a change.
To speed up propagation before a planned change, reduce your TTL to 300 seconds (5 minutes) at least 24–48 hours beforehand. After the change is confirmed, you can raise the TTL again.
DNS resolvers cache records independently. When you update a DNS record, each resolver retains the old value until its cached copy expires (based on the TTL). During this window, different users worldwide may see different results — this is normal and temporary.
Cloudflare (1.1.1.1), Google (8.8.8.8) and Quad9 (9.9.9.9) each operate their own global caching infrastructure, so their propagation state can differ by minutes to hours depending on TTL settings.
DNS propagation typically takes between a few minutes and 48 hours, though most resolvers worldwide see the change within 1–4 hours. The actual time depends on the TTL (Time to Live) of the record being changed — a record with a 3600-second TTL can remain cached for up to one hour after you make a change. To speed up future changes, lower your TTL to 300 seconds a day before making an update, then restore it after propagation completes.
Each DNS resolver worldwide caches DNS records independently for the duration of the TTL. After a DNS change, resolvers with a cached copy of the old record continue returning it until their cache expires. This means different users — and different DNS resolvers like Cloudflare (1.1.1.1), Google (8.8.8.8), and OpenDNS — may temporarily see different answers. This is normal and resolves once all caches expire.
TTL (Time to Live) is the number of seconds a DNS resolver is allowed to cache a record before it must re-query the authoritative nameserver. A TTL of 3600 means the record can be cached for one hour. Lowering TTL before a planned DNS change minimises propagation time. Very low TTLs (under 60 seconds) increase query load on your nameservers, so restore a normal TTL (3600–86400) after your change has propagated.
Use a DNS propagation checker like this one to query multiple resolvers in different geographic regions simultaneously. If all locations return the new record, propagation is complete. You can also run manual checks using dig (Linux/macOS) or nslookup (Windows) against specific resolvers: dig @8.8.8.8 example.com A and dig @1.1.1.1 example.com A. Comparing results from multiple resolvers gives a reliable picture of propagation status.