Introducing PostScale -- email API for transactional, inbound, and masked addresses. PostScale

    DNS Propagation Explained

    Understand what DNS propagation is, why DNS changes take time to spread across the internet, and how to check propagation status for your domain.

    DNS propagation is the time it takes for DNS changes to spread across all DNS servers worldwide. When you update a DNS record, the change doesn't take effect instantly everywhere — resolvers around the world are still serving the old cached version until their cache expires.

    How DNS Propagation Works

    DNS is a distributed, heavily cached system. Here's what happens when you change a record:

    1. You update the A record for example.com from 192.0.2.1 to 198.51.100.1 in DNScale
    2. The authoritative nameserver (DNScale) immediately serves the new record
    3. Recursive resolvers (like Google DNS, Cloudflare DNS, ISP resolvers) still have the old record cached
    4. Each resolver keeps serving the old IP until its cached copy expires based on the TTL
    5. After the TTL expires, the resolver fetches the new record from the authoritative server
    6. Gradually, all resolvers worldwide pick up the change

    This process typically takes minutes to 48 hours, depending on the TTL and resolver behavior.

    What Affects Propagation Time

    TTL (Time to Live)

    The single biggest factor. If your record had a TTL of 3600 (1 hour), most resolvers will serve the old record for up to 1 hour after you make a change. If the TTL was 86400 (24 hours), it could take up to a full day.

    Resolver Caching Behavior

    Not all resolvers respect TTL exactly:

    • Some resolvers enforce a minimum TTL (e.g., they won't cache for less than 30 seconds)
    • Some enforce a maximum TTL (e.g., capping at 24 hours even if you set 7 days)
    • A few resolvers may cache slightly beyond the TTL

    ISP DNS Servers

    ISP-operated DNS resolvers sometimes cache more aggressively than public resolvers like Google (8.8.8.8) or Cloudflare (1.1.1.1). Users on these ISPs may see slower propagation.

    Nameserver Changes

    Changing nameservers (e.g., migrating to DNScale) involves the domain registrar, TLD servers, and root servers. This is the slowest type of DNS change, often taking 24–48 hours because NS records at the TLD level typically have long TTLs.

    Typical Propagation Times

    Change TypeTypical TimeWhy
    Record update (A, CNAME, MX, etc.)Minutes to hoursDepends on the previous TTL
    New record addedNearly instantNo old cache to expire
    Record deletedMinutes to hoursOld cached entries must expire
    Nameserver change24–48 hoursTLD NS records have long TTLs
    TTL reductionUp to the old TTLResolvers cache at the old, longer TTL first

    How to Check DNS Propagation

    Using dig

    Query different DNS resolvers to see what they're returning:

    # Query Google DNS
dig example.com @8.8.8.8
 
# Query Cloudflare DNS
dig example.com @1.1.1.1
 
# Query your authoritative server directly
dig example.com @ns1.dnscale.eu
 
# Check only the answer, short format
dig +short example.com @8.8.8.8

    If the authoritative server returns the new IP but public resolvers still show the old one, propagation is in progress.

    Comparing Multiple Resolvers

    # Quick propagation check across major resolvers
for ns in 8.8.8.8 1.1.1.1 9.9.9.9 208.67.222.222; do
  echo "$ns: $(dig +short example.com @$ns)"
done

    How to Speed Up DNS Propagation

    1. Lower TTL Before Making Changes

    The most effective technique. Reduce TTL 24–48 hours before your planned change:

    # Step 1: Lower TTL to 300 (5 minutes), wait for old TTL to expire
example.com.  300  IN  A  192.0.2.1
 
# Step 2: Make the actual change
example.com.  300  IN  A  198.51.100.1
 
# Step 3: After propagation, restore a longer TTL
example.com.  3600  IN  A  198.51.100.1

    2. Flush Your Local Cache

    Flush your DNS cache to see changes immediately on your own machine. This doesn't speed up global propagation, but lets you verify changes locally.

    3. Use DNScale's Anycast Network

    DNScale's anycast DNS network ensures that your authoritative servers respond quickly from geographically distributed points of presence. When a resolver's cache expires, it gets the fresh record from the nearest DNScale node with minimal latency.

    Common Propagation Misconceptions

    "DNS propagation takes 24–48 hours"

    This is the maximum for nameserver changes. For regular record changes with short TTLs, propagation typically completes in minutes.

    "There's nothing you can do to speed it up"

    Lowering the TTL before a change significantly reduces propagation time. With a 5-minute TTL, most resolvers will pick up your change within 5 minutes.

    "Propagation means DNS servers are syncing with each other"

    Recursive resolvers don't sync with each other. Each resolver independently caches records and fetches updates from authoritative servers when the cache expires. "Propagation" is really just caches expiring at different times.

    DNS Propagation and DNScale

    When you update records in DNScale:

    1. The change takes effect on DNScale's authoritative servers within seconds thanks to direct database replication (not traditional zone transfers)
    2. All DNScale edge nodes worldwide are updated simultaneously
    3. Resolvers that query any DNScale node will get the new record as soon as their cache expires

    This is faster than providers that rely on AXFR/IXFR zone transfers between servers, which can add additional delay before the authoritative servers themselves are consistent.

    Conclusion

    DNS propagation isn't a mysterious process — it's simply DNS caches expiring at different times around the world. By understanding TTL and planning changes in advance, you can minimize propagation delays. DNScale's anycast network and instant edge replication ensure that the authoritative side of propagation is as fast as possible.