WhatIP

DNS TTL and Propagation: Why Changes Take Time

When updating web hosting, migrating servers, or changing mail providers, waiting for DNS changes to take effect can be frustrating. You might see your new website immediately while a client or teammate across town still sees the old server.

This delay is due to two core networking concepts: DNS TTL (Time to Live) and DNS Propagation.

Understanding how DNS caching works—and how to manage TTL values—helps you execute smooth server migrations with minimal downtime.

1. What is DNS TTL (Time to Live)?

DNS TTL (Time to Live) is a setting in a DNS record that tells recursive DNS resolvers (like Google DNS, Cloudflare, or your local ISP) exactly how long they should store (cache) that record in memory before requesting a fresh copy from your authoritative name servers.

Think of TTL as an expiration date on a cached file:

  • High TTL (e.g., 86400 seconds / 24 hours): Resolvers keep the record saved for a full day. This reduces DNS query traffic to your server and speeds up site loading times for returning visitors.

  • Low TTL (e.g., 300 seconds / 5 minutes): Resolvers check back with your authoritative DNS server every 5 minutes for updates.

When you update an A record or MX record, resolvers that already have the old record saved in their cache will continue serving the old IP address until their TTL counter reaches zero.

2. What is DNS Propagation?

DNS Propagation is the time window it takes for updated DNS records to spread across all recursive resolvers and DNS servers worldwide.

Because millions of ISPs and public DNS providers operate independently across different time zones, DNS updates do not happen everywhere simultaneously. Propagation is not a single global switch; it is a gradual expiration process occurring across thousands of cached servers individually.

3. Key Factors Affecting DNS Propagation Speed

While TTL is the primary factor controlling propagation time, several operational behaviors can influence how quickly changes appear:

  1. Resolver Cache Overrides: Some local ISPs ignore low TTL values set by domain owners and enforce a minimum hardcoded cache time (often 1 to 2 hours) to conserve network bandwidth.

  2. Negative Caching: If a user visits your domain before a new DNS record is created, the resolver may cache the “NXDOMAIN” (does not exist) response for a set period.

  3. Browser and OS Caching: Local operating systems (Windows, macOS) and web browsers maintain their own internal DNS caches, independent of network resolvers.

4. How to Reduce Downtime Before Making DNS Changes

If you are planning a server migration or IP address change, you can prevent extended downtime by following this simple workflow:

[3-7 Days Before Migration]
Lower TTL to 300 seconds (5 mins)
           │
           ▼
[Migration Day]
Update DNS Records to New Server IP
           │
           ▼
[Post-Migration / Stable]
Raise TTL back to 86400 seconds (24 hrs)

  1. Lower the TTL in Advance: 24 to 48 hours before your planned migration, lower the TTL value on your existing records to 300 (5 minutes) or 600 (10 minutes).

  2. Perform the Migration: Update your A or CNAME records to point to your new IP address.

  3. Verify Global Propagation: Check if the new IP is live across global locations.

  4. Restore the TTL: Once traffic has successfully shifted, raise the TTL back to 86400 (24 hours) to maintain optimal performance.

5. How to Troubleshoot and Test DNS Propagation

When troubleshooting a recent change, do not rely solely on your local browser. Use a structured testing approach:

A. Check the Authoritative DNS Server

Query your domain’s authoritative name server directly to verify that your DNS provider has processed your updates correctly.

B. Flush Local DNS Cache

Clear your computer’s local DNS cache to ensure your OS isn’t serving an outdated IP:

  • Windows: Open Command Prompt and run ipconfig /flushdns

  • macOS: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

C. Use a Public DNS Lookup Tool

Compare results from multiple global resolvers to see how far propagation has progressed. Use DNS Lookup to inspect current public DNS results. You can use our free IP Address Lookup Tool to inspect your public network details and test connection paths, or verify global DNS resolution via the WhatIP Homepage.

Summary

Aspect High TTL (e.g., 86400s) Low TTL (e.g., 300s)
Primary Advantage Faster response times, less server load Fast record updates and easy migrations
Primary Disadvantage Slow propagation when making updates Increased DNS query traffic
Best Used For Stable sites with rarely changing IPs Planned site migrations, dynamic environments

Return to WhatIP