DNS TTL Explained: How Long a DNS Answer Can Be Cached

The six points in the video

This is a silent video. The headings, explanations and labels below reproduce the information on screen.

1. 1

   Step 1: TTL means time to live

   0:18

   For DNS, it describes the cache lifetime associated with a record.

   On-screen labels: DNS record; Cached answer; Cache lifetime.

2. 2

   Step 2: Caching avoids repeat lookups

   0:30

   A resolver can reuse an answer while its cache rules allow it.

   On-screen labels: Stored answer; Repeat request; Reuse period.

3. 3

   Step 3: Record changes need context

   0:42

   A resolver may still hold an earlier answer after the source changes.

   On-screen labels: Updated source record; Earlier cached value; Remaining lifetime.

4. 4

   Step 4: Lowering it is not retroactive

   0:54

   A shorter new TTL does not instantly remove previously cached answers.

   On-screen labels: Previous TTL; Existing caches; Planned timing.

5. 5

   Step 5: Use the provider settings

   1:06

   Available values and special handling can differ by record and provider.

   On-screen labels: Record type; Provider limits; Supported setting.

6. 6

   Step 6: Verify the actual result

   1:18

   Check authoritative records and relevant resolver answers during a change.

   On-screen labels: Authoritative answer; Cached resolver answer; Working service.

Common questions

Go further