Skip to content

Lower DNS TTL, Yet Some Visitors Still Reach the Old Server?

Read this article in ไทย 中文

Lower DNS TTL, Yet Some Visitors Still Reach the Old Server?

Changing the setting does not erase every cached answer

An IT team lowers TTL to five minutes and changes the website IP, yet some visitors see the old site. One explanation is that an answer cached before the reduction can remain under its original TTL. Separate what the authoritative service now publishes from what intermediary resolvers and client devices are using. Saving a DNS setting proves a configuration change, not that every visitor has moved.

TTL governs how long a DNS answer may be cached. Cloudflare explains the trade-off: longer values increase reuse of cached answers but delay the effect of changes. TTL is not a website file lifetime, does not copy a database and does not clear a CDN or browser content cache. An old page therefore calls for checking both the network destination and content caching.

A timing example that explains the confusion

Hypothetical example: a resolver caches the old IP at 09:00 with a TTL of 3,600 seconds. The team reduces the authoritative TTL to 300 seconds at 09:10 and changes the IP at 09:15. Assuming normal TTL handling and no early refresh, the original answer may remain usable until 10:00, not expire at 09:20. These numbers illustrate the mechanism; they do not guarantee synchronized changes across networks.

Sequence the work before changing the destination

Start with actual hostnames, such as the main domain, www and API, recording A, AAAA or CNAME types, current values, existing TTLs and owners. Preserve the authorized configuration and lower TTL early enough for relevant old cached answers to expire before changing the destination. Cloudflare migration preparation ties advance planning to the existing TTL. Do not reduce TTL and change IP together, then simply count five minutes from saving.

This plan concerns changing a website destination. A simultaneous DNS-provider or nameserver change needs a separate delegation and DNSSEC plan. Lowering an A-record TTL does not automatically lower every domain-related cache lifetime. A proxy or CDN may also control relevant values and behavior; check the actual mode before applying a DNS-only procedure.

Test DNS answers and real user transactions

Before routing live traffic, test the new server with the correct hostname, including TLS, login, forms, uploads and integrations within scope. After the change, record time, queried hostname, resolver, returned IP and website results from different networks. Compare these with authoritative DNS answers. One resolver returning the new value does not establish another resolver’s state, and a working home page does not prove successful data writes.

If some visitors still see the old site, check A versus AAAA and www separately from the main name. Determine whether DNS is still old or the new destination is serving cached content. If checked answers are correct but transactions fail, investigate the service and data instead of repeatedly changing DNS without evidence. Clearing a test device’s cache may help a local test; it does not clear all customers’ caches.

Retire the old server only when data and recovery are ready

While visitors can reach both servers, decide which system accepts writes and whether a controlled pause or a verified synchronization method is required. Two independently writable databases can diverge even if DNS eventually converges. Before reverting the IP, reconcile new-server transactions and confirm the old service is ready. A DNS rollback does not undo transactions and introduces another period of mixed cached answers.

Have responsible owners record that key service names work, data is complete and outstanding items are resolved or explicitly tracked before approving old-server retirement. For an IT/Cloud discussion with Chawinnix, bring the hostname register, original TTLs, data plan and test results, without passwords in general documents. The aim is an evidenced service migration, not a fixed completion guarantee based on one TTL value.

A computer linked by blue paths to two servers, with one path passing through a storage box

Sources

Back to all articles

Start the conversation

Tell us briefly what concerns you and our team will get back to you. What you send stays confidential.