Each domain name is assigned at least two nameservers, which contain the DNS records for the domain.
When a server elsewhere in the world makes a DNS query for your domain it will generally cache a local copy of those DNS records. This makes future requests faster as the server doesn’t have to contact the nameservers each time someone visits your website or sends an email.
This caching system is also the reason that changes to DNS are not immediately reflected on the internet.
When DNS records change, some internet providers, devices and servers may continue to use the old cached version until the cache expires.
Which means:
New website may be viewed by some users
Others may still see the old site
Temporary fallback to previous email routing settings
DNS propagation is the common name for how long it takes for old cached records to expire.
Factors that influence DNS propagation include:
Refresh times for ISP cache
Caching policies of DNS servers
TTL (Time To Live) configuration
DNS cache on local machines
Updates to global DNS network
Some DNS servers are quick to refresh (within minutes), some might hold on to a cached record for many hours.
It may take 24-48 hours for DNS changes to fully propagate as they are rolled out across thousands of servers around the world.
DNS propagation usually happens when you change:
Name servers
A-Records
Mail exchanger ( MX ) records
CNAME records
Webhosting Providers
Email routing preferences
While propagating, depending on the location of the user and the internet service provider, services may act differently.
DNS propagation is a normal function of the internet. Updates take some time to refresh globally as domain information is cached locally in DNS servers around the world.
Many DNS changes are much faster now, but 24–48 hours is plenty of time for old cached records to expire completely around the world.