WebFora.io

Glossary

What is TTL

Also: time to live, cache time, DNS TTL

TTL (time to live) is how long, in seconds, a DNS record may be cached before it's re-checked. It decides how fast changes spread: 300 = 5 minutes, 86400 = a day. Leave the default unless you are planning a move.

Every DNS record has a TTL — the number of seconds that resolvers around the world may remember the answer before asking your Nameservers (NS)Nameservers are the servers that hold your domain's DNS records. Changing them (usually two addresses like ns1.example.net) hands the whole DNS setup to a new provider — the simplest way to connect a domain to a website.→ again. A TTL of 3600 means an old value can linger for up to an hour after you change it; 86400 means up to a day. It's the «valid until» date on a cached copy. Low TTLs make changes visible faster but cause slightly more lookups; high TTLs are fine for records you never touch. This is the main reason DNS propagationDNS propagation is the time it takes for a DNS change to be seen everywhere, as caches around the world expire. Usually minutes to a few hours; nameserver changes can take up to 24–48 hours.→ isn't instant.

  • Planning to move the website or email? Lower the TTL to 300 a day before the switch, then raise it back.
  • «Auto» at Cloudflare and «1 hour» at most registrars are sensible defaults.
  • Nameserver changes at the registry use their own TTL (often 24–48 h) — you can't speed those up.

Where it comes up

Related terms

Order · €39Audit