DNS Propagation

It runs the same query against several public resolvers (Google, Cloudflare, Quad9 and a default resolver) at once so you can see whether a DNS change has reached all of them yet.

Usually minutes to a few hours, bounded by the record's TTL. A record with a 3600-second TTL can be cached for up to an hour after you change it.

Large sites often return several rotating IP addresses for load balancing, so resolvers legitimately hand back different subsets. That is normal, not a propagation problem.

Your device or network resolver may still hold the previous record until its TTL expires, and browsers cache DNS too. Lowering the TTL before a planned change and flushing local caches speeds up the switch.

Lower the record TTL well before you make the change so caches expire sooner, then apply the change. You cannot force third-party resolvers to drop a cached record early, so patience within the TTL window is still required.

On Windows run ipconfig /flushdns, on macOS restart the mDNSResponder service, and on Linux the exact command depends on the resolver in use. Restarting the browser also clears its own internal DNS cache.

Yes. Reducing the TTL a day or two ahead means resolvers cache the old value for only a short time, so when you cut over the new record is picked up quickly across most networks.