Blog/
How long does DNS propagation take?
Why DNS changes look “stuck,” how TTL works, and how to compare Google, Cloudflare, and Quad9 answers for free.
DNS does not update the whole internet at once. Resolvers cache answers until the TTL (time to live) expires. “Propagation” is really many caches expiring and refetching — often minutes, sometimes up to 24–48 hours for stubborn TTLs.
What controls the wait
- Record TTL on the old answer still cached by resolvers.
- Registrar / DNS host publish delay (usually seconds to a few minutes).
- Local OS and browser DNS caches.
- ISP resolvers that ignore low TTLs occasionally.
Compare public resolvers →
Google, Cloudflare, and Quad9 side by side.
Tips before you change records
Lower TTL to 300 seconds a day before a planned cutover, make the change, verify with multiple resolvers, then raise TTL again. For nameserver changes at the registrar, allow extra time — NS records are cached aggressively.