DNS propagation and TTL: why changes take time
You changed a DNS record and nothing happened. Your colleague sees the new value, you still see the old one. This is normal, and the word for it is misleading.
"Propagation" suggests that your change spreads across the internet. It does not. Your name server has the new answer immediately. What takes time is everybody else forgetting the old answer they stored.
What TTL means
Every DNS record carries a TTL (Time To Live), in seconds. It tells any resolver how long it may reuse the answer before asking again.
example.com. 3600 IN MX 10 mail.example.com.Here, 3600 means one hour. A resolver that fetched this record 59 minutes ago will ask again in a minute. One that fetched it a minute ago will keep the old value for 59 more. That is why the same record looks different from two places at once.
| TTL | Duration | Typical use |
|---|---|---|
| 300 | 5 minutes | Just before a planned change |
| 3600 | 1 hour | Common default |
| 86400 | 1 day | Records that rarely change |
How long to wait
- A new record that never existed: usually a few minutes. One catch: if someone asked for it before you created it, the "does not exist" answer is cached too, for a duration set in your zone's SOA record.
- A changed record: up to the old TTL. The value you lowered it to counts only after the old one has expired.
- Changed name servers (NS): often the slowest, with up to 48 hours quoted, because the parent zone sets its own TTL that you do not control.
If it has been far longer than the TTL, the cause is rarely propagation. Check that you edited the zone your NS records actually point to.
How to prepare a change
- One or two days ahead, lower the TTL of the record to 300 seconds.
- Wait for the old TTL to pass, so every cache has the short value.
- Make the change. Most of the internet now follows within five minutes.
- Check it works, then raise the TTL back up.
For an MX change, keep the old mailbox open for a few days anyway. Some servers do not respect TTL, and senders retry for days on their own schedule.
Checking what the world sees
dig example.com MX @1.1.1.1
dig example.com MX @8.8.8.8
dig example.com MX @ns1.yourprovider.comThe last line asks your name server directly, skipping every cache. If it shows the new value, your change is saved and the rest is only waiting. If it shows the old one, your change never landed.
Frequently asked questions
Can I speed up propagation?
Not after the fact. You can only prepare by lowering the TTL beforehand. Clearing your own computer's cache only changes what you see, not what others see.
Why do I see the old value when my colleague sees the new one?
You use different resolvers, which fetched the record at different times. Neither of you is wrong, and it resolves itself once the TTL expires.
Does a low TTL slow my site down?
A very low TTL means more lookups, each adding a few milliseconds for the first visitor to a given resolver. An hour is a fine everyday value, and five minutes is only needed around a change.
The domain check asks public DNS servers rather than your computer, so it is a quick second opinion while you wait.