What is time-to-live (TTL) in networking?
Time to live (TTL) refers to the amount of time or “hops” that a packet is set to exist inside a network before being discarded by a router. TTL is also used in other contexts, including CDN caching and DNS caching.
How does TTL work?
When a packet of information is created and sent out across the Internet, there is a risk that it will continue to pass from router to router indefinitely. To mitigate this possibility, packets are designed with an expiration called a time-to-live or hop limit. Packet TTL can also help determine how long a package has been in circulation and allow the sender to receive information about a packet’s path through the Internet.
Each packet has a place where it stores a numerical value determining how much longer it should continue to move through the network. Every time a router receives a packet, it subtracts one from the TTL count and then passes it onto the following location in the network. If, at any point, the TTL count is equal to zero after the subtraction; the router will discard the packet and send an ICMP message back to the originating host.
The commonly used network commands ping and traceroute both utilize TTL. When using the traceroute command, a stream of packets with increasingly higher sequential TTLs is sent across the Internet toward a destination. Because each step along the connection is the last stop for one of the packets, each location will return an ICMP message to the sender after discarding the packet. The time it takes for the ICMP message to return to the sender is then used to determine how long it takes to get to each next hop along the network.
In what other circumstances is TTL used?
Besides tracing the route packets take across the Internet, time-to-live is used in caching information for a set period. Instead of measuring time in hops between routers, each of which can take a variable amount of time, some networking use cases operate more traditionally.
CDN’s like Cloudflare’s CDN commonly use a TTL to determine how long cached content should be served from a CDN edge server before a new copy will be fetched from an origin server. A CDN can do updated content without requests continuously propagating back to the origin by adequately setting the amount of time between origin server pulls. This optimization allows a CDN to efficiently serve content closer to a user while reducing the bandwidth required from the origin.
In the context of a DNS record, TTL is a numerical value that determines how long a DNS cache server can serve a DNS record before reaching out to the authoritative DNS server and getting a new copy of the record.
