TTL and caching

Published September 4, 2026. Updated September 9, 2026.

Every DNS record has a TTL (time to live): how many seconds a resolver may cache it before asking again.

A long TTL means fewer lookups and faster responses, but changes take longer to reach everyone. A short TTL propagates changes quickly but increases query load. Before a planned change, lower the TTL a day ahead so the switch takes effect quickly, then raise it again afterwards.

See also