Glossary

TTL

Time to live: how many seconds resolvers may cache a DNS record before asking again.

In plain English How long other computers may remember a domain setting before checking again, in seconds. Short means changes show up faster.

TTL (time to live) is measured in seconds. It is the number of seconds a DNSDNS The internet’s phone book. It turns a name people can remember, like example.com, into the number address computers use to find the server. More about DNS → answer may be cached. Every DNS record has one. A resolver that looks up your record keeps the answer for that long before asking again, so the TTL decides how quickly a change to the record is seen around the world.

Common values

TTLEqualsUse
3005 minutesBefore and during a planned change
36001 hourA sensible default
864001 dayRecords that almost never change

The trade-off

A long TTL means fewer lookups and slightly faster sites for returning visitors, but changes take up to that long to reach everyone. A short TTL makes changes fast, at the cost of more lookups. There is little benefit in going below 300; some resolvers raise very short values anyway.

Planning a change

The TTL that matters is the one set before the change, because that is what resolvers already cachedCache A saved copy of something, kept so it does not have to be made or fetched again. Like keeping a printed copy instead of reprinting it for every person who asks. More about Cache →. To move a site quickly:

  1. Lower the record’s TTL to 300 at least one full old-TTL period in advance.
  2. Make the change; it spreads within about five minutes.
  3. Raise the TTL back afterwards.

See what DNS propagation is.

See it count down

dig example.com A +noall +answer

The number before IN A is the remaining TTL on your resolver’s cached copy. Ask your domain’s own nameserverNameserver The server that holds all of a domain’s settings. Whoever runs your nameservers controls where your website and email point. More about Nameserver → instead, with @ns1.your-dns-host.com, to see the full configured value.

Questions people ask

Is TTL in seconds or minutes?

Seconds. A TTL of 3600 means one hour, 300 means five minutes and 86400 means one day. Some DNS dashboards show a menu of friendly values like “1 hour”, but they store and send the value in seconds.

What is a good TTL?

3600 (one hour) for most records. Lower it to 300 a day before a planned move, then raise it again afterwards.

Does lowering the TTL make DNS changes instant?

Only for resolvers that fetch the record after you lowered it. Copies already cached keep the old TTL until they expire, which is why you lower it in advance. See DNS propagation.

See what resolvers around the world return for a record with the free DNS propagation checker.