You just updated your domain's DNS records. Maybe you pointed your site to a new hosting provider, switched email services, or added a CNAME record for a subdomain. You hit save, refresh your browser, and... nothing has changed. The old site is still showing up. The new email is not working yet. What is going on?

The answer, almost every time, is DNS propagation. It is the reason your DNS changes do not take effect the moment you make them, and understanding how it works can save you hours of confusion and unnecessary troubleshooting.

What Is DNS Propagation?

DNS propagation is the process by which updated DNS records spread across the global network of DNS servers. When you change a record -- say you update an A record to point your domain to a new server -- that change starts at your domain's authoritative nameserver. From there, it needs to reach every recursive DNS resolver around the world that has cached the old version of your record.

There is no single switch that flips all at once. Instead, thousands of DNS resolvers independently discover the updated record at different times. Some pick it up in minutes, others take hours. That staggered process is what people mean when they talk about DNS propagation.

Why It Takes Time

The delay comes down to caching. DNS resolvers do not query the authoritative nameserver for every single request they receive. That would be incredibly slow and would overwhelm nameservers with traffic. Instead, when a resolver looks up a record for the first time, it stores -- or caches -- the result for a set period. During that window, it serves the cached version to anyone who asks, without checking whether the record has changed.

This caching behavior is by design. It makes DNS fast and efficient for the vast majority of lookups. But when you change a record, every resolver that has already cached the old version will keep serving it until the cache expires. Only then will it query the authoritative nameserver again and pick up your new record.

The result is a transition period where some users see the updated record and others still see the old one. This is perfectly normal.

How TTL Controls the Speed

The length of time a DNS resolver caches a record is determined by the record's TTL, or Time to Live. TTL is a value, measured in seconds, that you set on each DNS record. It tells resolvers how long they are allowed to cache that record before they must check for a fresh copy.

Here is how common TTL values translate:

300 seconds -- 5 minutes. Resolvers will refresh the record frequently. Good for records you expect to change often.
3600 seconds -- 1 hour. A common default for many DNS providers. A reasonable balance between performance and flexibility.
86400 seconds -- 24 hours. Resolvers will hold onto the cached record for a full day. Good for records that rarely change, but slow to propagate when they do.

If your record had a TTL of 86400 seconds (24 hours) before you made a change, resolvers that cached the old record within the last 24 hours will continue serving it until their cache expires. That is why propagation can take up to 24 or even 48 hours in some cases.

How to Speed Up Propagation

You cannot force every DNS resolver in the world to clear its cache on demand, but there are practical steps you can take to minimize the wait:

Lower the TTL before making changes. This is the most effective strategy. A day or two before you plan to update a record, drop its TTL to something short -- 300 seconds is a solid choice. Wait for the old TTL period to pass so that all resolvers pick up the new, shorter TTL. Then make your actual record change. Because resolvers are now refreshing every five minutes, the new record will spread much faster.
Wait for the old TTL to expire. If you forgot to lower the TTL in advance, the old value is still in effect. Check what the previous TTL was and use that as your estimate for how long propagation will take. There is no shortcut around this.
Flush your own DNS cache. While you wait for global propagation, you can clear the DNS cache on your own computer or browser to see the updated record sooner. This only affects your device -- it does not speed up propagation for anyone else -- but it lets you confirm the change is live on the authoritative nameserver.

How to Check Propagation Progress

Rather than guessing whether your DNS changes have taken effect, you can actively verify them. There are a few reliable ways to do this:

Use a DNS lookup tool. Enter your domain into our DNS lookup tool to see the current records being returned. This queries DNS resolvers directly, so you can confirm what values are being served right now.
Query the authoritative nameserver directly. If you are comfortable with the command line, you can use dig to check your record against the authoritative nameserver: dig @ns1.yourdns.com example.com A. If the correct value shows up here, the change is live at the source -- it just needs time to propagate outward.
Test from multiple locations. Because different resolvers around the world cache independently, a record might resolve correctly from one location and still show the old value from another. Testing from several geographic locations gives you a clearer picture of how far propagation has progressed.

Common Scenarios That Involve Propagation

Propagation is not limited to one type of change. Here are some of the situations where you will encounter it:

Switching web hosts. When you update your A record or CNAME record to point to a new hosting provider, the old site may continue to appear until propagation completes.
Changing nameservers. If you move your domain's nameserver delegation to a different DNS provider, this is one of the slower changes to propagate because the nameserver records themselves are cached at the registry level.
Setting up email. Adding or updating MX records for a new email service means some senders will route to the old server until their resolvers refresh.
Adding verification records. When a service asks you to create a TXT record for domain verification, propagation delays can cause the verification check to fail on the first attempt. Waiting 15 to 30 minutes and retrying usually resolves the issue.

Stay Patient and Plan Ahead

DNS propagation is one of those topics that trips up newcomers and experienced administrators alike. The key takeaway is that propagation is not a bug or a misconfiguration -- it is how DNS is designed to work. Caching makes the internet fast, and the trade-off is that changes take time to reach everyone.

The best approach is to plan ahead. Lower your TTL before making changes, verify your updates using a DNS lookup tool, and give the process time to complete. If you understand how TTL values control caching and how resolvers work, you will never be caught off guard by a propagation delay again.

DNS Propagation Explained: Why Your Domain Changes Take Time