DNS Propagation Check

What "Propagation" Actually Means

DNS doesn't really "propagate" in the usual sense — nothing is pushed to other resolvers. What actually happens is that recursive resolvers around the internet hold cached copies of your old record until their TTL expires, at which point they query your authoritative nameservers again and pick up the new value. If you set a TTL of 3600 seconds, it can take up to an hour for every resolver to catch up; if you set a TTL of 60 seconds before a cutover, most resolvers will catch up within a minute. This tool checks four well-distributed public resolvers at once so you can see the rollout in near-real time.

Why Four Different Resolvers

Each resolver has its own cache, its own topology, and its own upstream behavior. Cloudflare (1.1.1.1) and Google (8.8.8.8) are the two biggest public resolvers and serve most consumer traffic. OpenDNS (Cisco) and NextDNS are widely used in managed filtering deployments. If all four agree, you can be confident the change is live for most of the internet. If one disagrees, you can see which and how.

Planning a Cutover

The safe cutover pattern is: lower the TTL to 60 seconds at least a full old-TTL before the change, make the switch, watch this page until all resolvers show the new value, then raise the TTL back to a normal value. I help clients plan zero-downtime DNS cutovers, nameserver migrations, and mail platform moves. See migration services or get in touch.