DNS propagation is the time it takes for a record change to be seen across the internet. Changes are not instant because resolvers cache answers, so different networks may see old data for a while after you edit a record.
Typical Timeframes
- Record edits (A, CNAME, MX, TXT): usually a few minutes to a few hours, often within four hours.
- Nameserver changes: can take up to 24 to 48 hours to complete globally.
- Most users: typically see updates within a couple of hours.
What Affects the Speed
- TTL: the Time To Live on a record sets how long resolvers cache it. A lower TTL means faster future changes.
- Resolver caching: some ISPs hold cached answers longer than the TTL suggests.
- Registry refresh: nameserver changes depend on the domain registry updating, which adds time.
How to Speed Things Up
- Lower the TTL on a record a day before you plan to change it, so caches expire sooner.
- Flush your local DNS cache after the change to test from your own machine.
- Test from multiple networks or a propagation checker rather than relying on a single device.
Propagation cannot be forced to complete everywhere at once because you do not control third-party caches. Plan changes ahead of time, and avoid changing nameservers right before an event when downtime would be costly. If a change still has not appeared after 48 hours, recheck the record for errors.