Updating a DNS record and seeing no immediate change is one of the most common sources of confusion after a domain migration or hosting change. Propagation delay, not a mistake in the update itself, is almost always the actual cause. This guide explains why propagation takes time and exactly how to check, using a free dns lookup, whether a specific change has actually gone through yet.
Why DNS Changes Do Not Apply Instantly Everywhere
DNS records are cached at multiple layers across the internet, your own internet service provider, intermediate DNS resolvers, and individual devices, each holding onto a previous record value for a specific duration called the TTL, or time to live, meaning a change only fully propagates once every one of these caches has expired and refreshed with the new value.
What TTL Actually Controls
TTL, set on each individual DNS record, specifies exactly how long a resolver is permitted to cache that record’s value before checking for an update, meaning a record with a 24-hour TTL can take up to a full day to reflect a change everywhere, while a record with a shorter TTL propagates considerably faster once updated.
| Factor | What It Controls | Practical Implication |
| TTL setting | How long resolvers cache a record | Lower TTL before a planned change speeds up propagation |
| ISP caching | Local resolver behavior outside your control | Some regions update faster than others |
| Record type changed | Different records may propagate differently | MX changes can lag behind A record changes |
Checking Whether Your Change Has Actually Propagated
Running your domain through a free dns lookup from wherever you are checking shows the current record value that specific lookup point sees, and comparing this result over the following hours reveals whether the new value is actually spreading or whether the old value is still being served in your specific location.
Confirming which specific IP address a domain currently resolves to with an ip lookup helps verify whether traffic is genuinely reaching the new server yet, a useful cross-check beyond the raw DNS record lookup alone.
Speeding Up Future Propagation
Lowering a record’s TTL several days before a planned DNS change, then restoring it to a normal value once the change is complete and confirmed, meaningfully reduces propagation delay for that specific future change, since resolvers will already be checking for updates more frequently by the time the actual change occurs.
What to Do If a Site Feels Slow During This Window
Checking whether slow load times during a propagation window stem from DNS delay itself or from an unrelated performance issue on the new server requires running a page speed checker against the new destination directly, isolating DNS propagation delay from genuine server-side performance problems that a propagation issue alone would not actually cause.
Every tool referenced in this guide is available through WritoryBuzz’s free DNS and performance tools, and the same tools page covers ongoing monitoring needs beyond a single migration event.
