Domain Name System (DNS) Propagation Explained

Why Changes Are Not Instant

When you update a DNS record, that change does not immediately appear everywhere on the internet at once. Instead, it spreads gradually across a global network of DNS servers in a process called propagation. If you have not yet read DNS Management: A/CNAME/MX/TXT Records Explained, it covers what these records actually do before this article explains why changes to them take time to apply everywhere.

How Propagation Actually Works

Internet service providers and other networks maintain their own DNS servers, which store, or cache, DNS information for a set period of time to avoid looking up the same information repeatedly. When you update a record, some servers around the world pick up the new information quickly, while others continue serving the previously cached version until their cache naturally expires.

How Long Propagation Typically Takes

Most DNS changes become visible within a few hours, though full global propagation can occasionally take up to twenty four to forty eight hours in less common cases. The exact timing depends on the specific record's time to live setting, which determines how long other servers are permitted to cache that record before checking for updates again.

What Time to Live (TTL) Means

Every DNS record includes a TTL value, expressed in seconds, that tells other servers how long they should cache that record before checking for changes again. A lower TTL means servers check for updates more frequently, allowing changes to propagate faster, while a higher TTL means better performance through caching but slower propagation when a change is made.

Planning Ahead for Time Sensitive Changes

If you know in advance that you will be making a significant DNS change, such as migrating to a new server, consider lowering the TTL value on the relevant record several hours or a day before the actual change. This shortens the caching window in advance, so that when you do make the actual change, it propagates more quickly than it would with a longer standard TTL.

Why Your Site Might Look Different to Different Visitors Temporarily

During the propagation window, it is normal and expected for some visitors to reach your old server while others reach your new one, depending on which cached DNS information their specific network is currently using. This is not an error and resolves on its own as caches naturally expire and refresh with the updated information.

Checking Propagation Status

Several free online tools allow you to check how a specific DNS record currently appears from various locations around the world, giving you visibility into how far a recent change has propagated at any given point.

When to Be Concerned

If a DNS change has not shown any signs of propagating at all after forty eight hours, this suggests the change may not have been saved correctly, rather than simply being a slow but normal propagation delay. In that case, revisit Managing DNS Zones in cPanel/Plesk to confirm the record was actually updated as intended.