DNS Propagation: Why DNS Changes Take Time
DNS propagation is the delay between changing a DNS record and every resolver on the internet seeing the new value. The name is misleading: nothing propagates outward. Resolvers around the world cache your old record for as long as its TTL (time to live) allows, and each cache expires on its own schedule — propagation is just caches timing out.
What actually determines the wait
- •Record TTL: a record cached with a 3600-second TTL can be served stale for up to an hour after you change it; long TTLs mean long waits.
- •Nameserver changes are slower than record changes: the TLD's delegation records carry their own TTL (commonly up to 48 hours), which is where the "24-48 hours" folk wisdom comes from.
- •Some resolvers ignore or clamp TTLs, so stragglers can lag beyond the theoretical window.
Working with it, not against it
Before a planned migration, lower the TTL on affected records to something short (say 300 seconds), wait out the old TTL, make the change, then raise the TTL again. For domain sales, expect a buyer's new nameservers to take up to a day or two to be seen universally — that is normal, not a problem with the transfer.
Frequently Asked Questions
How long does DNS propagation take?
For ordinary record changes, up to the record's TTL — minutes to hours. For nameserver (delegation) changes, up to about 48 hours, though most resolvers see it much sooner.
Can I force DNS propagation to finish faster?
You cannot flush other people's caches. You can lower TTLs in advance, and you can flush specific public resolvers (Google and Cloudflare offer purge tools) to help the resolvers most users rely on.