DNS propagation is the time it takes for DNS changes to update across internet providers, DNS resolvers, and devices worldwide after you modify records such as nameservers, A records, MX records, or CNAME records.
Although changes can appear quickly in some places, full global propagation takes longer.
Typical DNS propagation times:
A few minutes for some users1 to 6 hours for many updatesUp to 24 hours in common casesUp to 48 hours in slower or cached networksSome users may see the new result while others still see the old one during propagation.
TTL tells DNS resolvers how long to cache records.
Examples:
300 seconds = faster refresh3600 seconds = 1 hour86400 seconds = 24 hoursLower TTL usually means faster future changes.
Different updates may propagate differently:
A / AAAA Record – often fasterCNAME – similar to A recordsMX Record – may take longer to fully reflect everywhereNameserver Change – often longest and most noticeableInternet providers and public resolvers may cache old data longer than expected.
Examples:
Local ISP DNS
Router cache
Device cache
Browser cache
Some regions update faster than others depending on resolver networks.
DNS Change | Common Time |
|---|---|
A Record | Minutes to 24h |
CNAME | Minutes to 24h |
MX Record | 1h to 24h |
TXT Record | Minutes to 24h |
Nameserver Change | 2h to 48h |
Old website in one location
New website in another
Email routing inconsistency
SSL mismatch temporarily
Intermittent access
This is normal during transition.
Before planned changes:
Lower TTL 24 hours earlier (if possible)
Prepare new DNS records first
Change during low-traffic hours
Keep old hosting active temporarily
Use:
DNS checker tools
nslookup / dig commands
Test on mobile data vs Wi-Fi
Different geographic networks
Different DNS cache or network resolver.
Sometimes visible quickly, but global consistency is rarely instant.
Usually you must wait for caches to expire.
For important migrations:
Do not cancel old hosting immediately
Keep both environments ready
Wait full propagation window