When you change DNS settings for a domain, the changes are not visible everywhere immediately.
Some users may see the new website or service within minutes, while others may continue seeing the previous configuration for several hours. This delay is commonly referred to as DNS propagation.
Although DNS changes often become visible quickly, full propagation can take up to 48 hours in some situations.
Table of Contents
What Is DNS Propagation?
DNS propagation is the process by which DNS changes become visible across different networks and DNS resolvers worldwide.
When you update a domain’s DNS records, the new information must gradually replace older cached records stored by internet service providers, public DNS services, and local devices.
During this period, different users may receive different DNS responses for the same domain.
Why Does Propagation Take Time?
The main reason is DNS caching.
To improve performance and reduce the number of DNS lookups, DNS resolvers temporarily store DNS records in a cache.
Instead of requesting fresh information every time someone visits a website, the resolver can use the cached data until it expires.
As a result, some DNS servers continue using older records until their cache is refreshed.
What Is TTL?
TTL (Time To Live) is a value assigned to a DNS record.
It determines how long a DNS resolver can keep that record in its cache before checking for an updated version.
For example:
- A TTL of 300 seconds allows records to refresh after 5 minutes.
- A TTL of 3600 seconds allows records to refresh after 1 hour.
Lower TTL values can help DNS changes become visible more quickly, but they also increase the number of DNS queries.
What Happens During Propagation?
After a DNS change is made:
- The authoritative DNS servers are updated.
- Existing cached records continue to be used until they expire.
- DNS resolvers request fresh information when the cache expires.
- Users gradually begin receiving the updated DNS records.
This is why one user may see a new website while another still sees the previous version.
Common DNS Changes That Require Propagation
DNS propagation can occur after:
- Changing nameservers
- Updating an A record
- Updating an AAAA record
- Changing MX records for email
- Adding or removing CNAME records
- Connecting a domain to a new hosting provider
The visibility of these changes depends on cache expiration across different DNS resolvers.
DNS Propagation vs. Website Migration
DNS Propagation ≠ Website Migration
Website migration involves moving website files, databases, or applications.
DNS propagation involves updating the information that tells users where those services are located.
A website can be fully migrated while DNS propagation is still in progress.
Practical Implications
DNS propagation is normal behavior and does not necessarily indicate a problem.
During propagation:
- Some visitors may reach the old website.
- Others may reach the new website.
- Email delivery may temporarily follow old or new routes depending on cached DNS records.
Because propagation depends on cache expiration across multiple networks, there is usually no way to force every user to receive updated DNS information immediately.
Summary
DNS propagation is the period during which DNS changes gradually become visible across the internet. The delay is primarily caused by DNS caching, which allows DNS resolvers to store records temporarily before requesting updated information. While many changes become visible within a few hours, full propagation can occasionally take up to 48 hours depending on DNS cache settings and network conditions.