What TTL means
TTL stands for time to live. It is a number of seconds attached to each DNS record, telling resolvers how long they may keep the answer before asking your nameservers again. A record with a TTL of 3600 can be cached for up to an hour.
Panels show it in different ways. Some want raw seconds, some offer a dropdown of minutes and hours, and some have an "Automatic" setting that picks a value for you. These are the values you will meet most often:
| Seconds | Which is | Typical use |
|---|---|---|
| 300 | 5 minutes | Just before and during a planned change |
| 3600 | 1 hour | A sensible everyday value |
| 14400 | 4 hours | The cPanel default |
| 86400 | 1 day | Records that almost never change |
Low or high: the trade-off
A low TTL means changes reach visitors quickly, and so do fixes when you make a mistake. The cost is that resolvers come back to your nameservers more often. That adds a small delay to more visits, and it leaves less of a cushion if your DNS provider has an outage, because cached answers run out sooner.
A high TTL is the reverse: fewer lookups and more resilience, but every change, and every typo, lingers for as long as the TTL says.
For most sites an hour is a good everyday setting for records that might change, such as the A record for the website. Records that rarely move, such as MX and TXT, are fine at an hour or higher. There is no prize for the lowest number.
Lower it before a change, not after
The useful trick is to shorten the TTL ahead of a planned change. The timing is the part people get wrong:
- Lower the TTL to 300 seconds and save. Change nothing else yet.
- Wait at least as long as the old TTL. Caches are still holding the record with its old, long TTL. If it was four hours, wait four hours. Doing this the day before covers almost every case.
- Make the real change. Every cache now refreshes within five minutes, and if something is wrong you can switch back just as fast.
- Raise the TTL again once you are happy with the result.
Lowering the TTL at the same moment as the change, or afterwards, achieves nothing for that change. The old answer is already cached on the old clock. This is the heart of moving a website without downtime.
Panels differ in how low they let you go. If 300 is refused, use the lowest value on offer: our GoDaddy guide uses 600. On Cloudflare, proxied records are fixed at "Auto", which is 300 seconds.
What TTL does not control
- Nameserver changes. The record that says which nameservers run your domain is published by the domain registry with a TTL of its own. For .com it is 48 hours. Lowering the TTLs in your zone does not shorten it.
- Names that did not exist. If a resolver looked up a name before you created it, it remembers the "not found" answer for a time set by the zone's SOA record, not by the new record's TTL.
- Your own devices. Browsers, operating systems and routers keep short caches of their own. Flush them or test from another network before blaming the record.
- Slow publishing. Some providers take a while to push an edit to their own nameservers, whatever the TTL. The provider guides flag the ones that do.
All of this is why "DNS propagation" feels unpredictable. How long propagation really takes goes through each case.
How to see the TTL you have now
In your DNS panel, the TTL is a column or field beside each record. The provider guides show where each panel keeps its DNS editor. From a terminal, ask one of your own nameservers, so you see the configured value and not a cache counting down:
dig NS yourdomain.com +short
dig @ns1.your-dns-provider.com yourdomain.com A
The number after the name in the answer line is the TTL in seconds. Ask a public resolver instead (dig @1.1.1.1 yourdomain.com A) and the same column shows how many seconds that resolver has left before it fetches a fresh copy. Run it twice and you can watch it fall.
If you would sooner not use a terminal, the Route Planner checks your records against live DNS, and the troubleshooting page covers what to do when the answer is not the one you expected.



