{"id":1485,"date":"2026-09-03T12:16:49","date_gmt":"2026-09-03T06:46:49","guid":{"rendered":"https:\/\/cpanelfree.com\/blog\/what-is-dns-ttl-best-values-before-migration\/"},"modified":"2026-09-03T12:31:16","modified_gmt":"2026-09-03T07:01:16","slug":"what-is-dns-ttl-best-values-before-migration","status":"publish","type":"post","link":"https:\/\/cpanelfree.com\/blog\/what-is-dns-ttl-best-values-before-migration\/","title":{"rendered":"What is DNS TTL (Time to Live) and What Value Should You Set Before Migration?"},"content":{"rendered":"
\n

\n Quick Answer:<\/strong> DNS TTL (Time to Live)<\/strong> is a numerical value (measured in seconds) that tells recursive DNS resolvers and ISP caching servers how long to cache a DNS record before requesting fresh data from the authoritative nameserver. 24 to 48 hours before migrating a website<\/strong>, you should lower your A record TTL to 300 seconds (5 minutes)<\/strong> to ensure visitors switch to your new server IP almost instantly upon migration.\n <\/p>\n<\/div>\n

How DNS TTL Works Under the Hood<\/h2>\n

Every DNS record (A, CNAME, MX, TXT) includes a TTL integer. When a user in London queries your website, their local ISP resolver caches your server IP address for the duration of the TTL. If your TTL is set to 86400<\/code> (24 hours), the ISP will not check your authoritative nameservers again for a full day.<\/p>\n

If you migrate to a new server IP while your TTL is 24 hours, users will continue sending database transactions and eCommerce orders to your obsolete old server for up to 24 hours, resulting in split-brain data loss.<\/p>\n

The 3-Phase TTL Migration Strategy<\/h2>\n

Phase 1: Pre-Migration (24\u201348 Hours Before Migration)<\/h3>\n

Access your DNS editor (cPanel Zone Editor, Cloudflare, or Route 53) and lower the TTL on your primary records:<\/p>\n\n\n\n\n\n\n
Record Name<\/th>\nStandard Production TTL<\/th>\nPre-Migration Target TTL<\/th>\n<\/tr>\n<\/thead>\n
Root Apex (@) A Record<\/td>\n86,400s (24 Hours)<\/td>\n300s (5 Minutes)<\/strong><\/td>\n<\/tr>\n
www CNAME \/ A Record<\/td>\n86,400s (24 Hours)<\/td>\n300s (5 Minutes)<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Phase 2: Migration Cutover Day<\/h3>\n

Once the old 24-hour cache window has elapsed, import your final database dump to the new server and update the A record to your new server IP. Because the TTL is 300 seconds, 99% of global traffic shifts to the new server in under 5 minutes<\/strong>.<\/p>\n

Phase 3: Post-Migration Stabilization<\/h3>\n

After verifying site stability for 48 hours on the new server, restore your TTL back to 86,400 seconds (1 day)<\/strong>. This reduces unnecessary DNS query traffic to your nameservers and speeds up browsing for repeat visitors.<\/p>\n

Understanding DNS Caching Hierarchies (Browser, OS, ISP, Root)<\/h2>\n

When a DNS lookup occurs, cached data is stored at 4 distinct hierarchical layers, each governed by TTL rules:<\/p>\n

    \n
  1. Browser DNS Cache:<\/strong> Google Chrome and Firefox cache IPs in memory for 60 seconds regardless of TTL.<\/li>\n
  2. Operating System Resolver Cache:<\/strong> Windows DNS Client and macOS mDNSResponder cache records based on record TTL.<\/li>\n
  3. Local Router & ISP Cache:<\/strong> Network gateways and ISP recursive servers cache records up to the full TTL duration.<\/li>\n
  4. Authoritative Nameservers:<\/strong> The ultimate source of truth holding your master DNS zone file.<\/li>\n<\/ol>\n

    Lowering your TTL to 300s ensures that layers 2 and 3 purge obsolete data almost instantaneously.<\/p>\n

    Negative TTL and SOA Record Tuning<\/h2>\n

    The Start of Authority (SOA) record contains a Minimum TTL (Negative Caching TTL)<\/strong> value. If an external resolver queries a non-existent subdomain (NXDOMAIN), this setting dictates how long the failure state is cached. Keep this value between 300s and 3600s during active migration windows.<\/p>\n

    Analyzing Real-World Bandwidth and Server Load Impact of TTL Settings<\/h2>\n

    Setting DNS TTL involves a fundamental engineering trade-off between traffic agility<\/strong> and nameserver infrastructure load<\/strong>:<\/p>\n