TTL

TTL, or Time To Live, indicates how long a DNS record may be cached by resolvers and other systems before it must be re-requested. Typically expressed in seconds, it is published with the record within the DNS zone. For example, a TTL of 3600 means one hour of expected cache duration. The TTL does not indicate domain registration length, certificate expiration, or server lifetime. Each service uses its own caching policies, so visibility of changes may vary accordingly.

Cache and Updates

When a resolver receives a DNS record, it stores it until the TTL expires or per its internal policies. During this time, it may respond with an older value even if the authoritative zone has already been updated. A resolver without the record in cache queries the authoritative nameservers to retrieve current data. Thus, a direct query to the authority and a public resolver query can show different values without the new record being ignored. Record which server was queried and when.

The TTL is set by the zone administrator and may vary for each record. Longer TTLs reduce query volume and improve cache efficiency, but slow propagation of planned changes. Shorter TTLs allow faster updates in some cases, but increase load and do not guarantee all resolvers will respect them exactly. The TTL should be chosen based on service stability, change plans, and infrastructure capabilities—not always set to the minimum.

Planning a Migration

Before making DNS changes, it is advisable to lower the TTL in advance, allowing existing caches time to learn the new short value. Only after this step should the address or target be modified. If the TTL is reduced at the same time as the record, those who have already cached the previous TTL will continue using it for the remainder of its duration. Once migration is stable, the TTL can be restored to an appropriate level. This process must be coordinated with web services, email systems, APIs, and any other services linked to the zone.

A low TTL does not fix incorrect records, wrong nameserver delegation, or unresponsive servers. If the new endpoint fails to respond, users who update their cache first may see the error first. To reduce risk, both destinations may need to operate in parallel during the transition. Verify authoritative responses and test applications from different networks, as browsers and operating systems may add their own caching layers.

TTL in Other Contexts

The acronym TTL is also used in other computing contexts, such as IP packets or application-level caches, with related but distinct meanings. In a DNS panel, the value usually refers to the specific record. A CNAME record and its resolved target may have different TTLs, and the final response depends on multiple caching layers. DNSSEC and negative responses introduce additional parameters that can affect data storage duration.

In summary, TTL defines the expected cache duration for DNS information. It governs update timing and load but is not an instant propagation command. Effective management involves planning ahead of migrations and verifying responses from both authorities and resolvers.