Example 1
- 3600 s
3600
How many seconds at TTL 3600? 3600. A typed conversion, not a DNS query.
DNS TTL Calculator
Type a TTL in seconds. 3600 stays 3600. 60 stays 60. 86400 stays 86400. A number conversion, not live DNS.
This converts the seconds you type. The calculator does not query a nameserver. The pool start sits on DHCP range.
Results
Enter data and click Calculate.
How it works
DNS TTL Calculator in this calculator shows the seconds you type. 3600 stays 3600. 60 stays 60. 86400 stays 86400. Minutes, hours, and days sit beside that same number. The calculator does not make a DNS query.
Field dns-ttl-a is a second count. 3600 / 60 = 60 minutes, / 3600 = 1 hour. 60 is one minute. 86400 is one day. The extras result stays the integer seconds.
3600 does not come from dig. 60 is not an SOA from Cloudflare. 86400 is not resolver cache. You type the TTL. There is no live lookup.
DHCP range next door times a pool start. IP subnet counts hosts. Here 3600 stays 3600, the second conversion alone.
Type 3600, then Calculate. The result is 3600. Switch to 60 or 86400. Zero seconds stay 0. A blank field does not count.
3600 stays 3600. 60 stays 60. 86400 stays 86400. Another number in the field changes the result.
Formula
seconds = entry; minutes = s/60; hours = s/3600; days = s/86400. No DNS query.
How to use
- Type 3600 in the TTL field.
- Click Calculate. The seconds result is 3600.
- 60 stays 60. 86400 stays 86400.
- A seconds conversion, not live DNS.
- The next card times a DHCP pool start.
3600 stays 3600
Seconds from the field. 3600 stays 3600. Not a DNS query.
- DNS
- No lookup. 60 stays 60. Not dig and not SOA.
- TTL
- Typed seconds. 86400 stays 86400. Not resolver cache.
- Calculator
- The calculator result. 3600 stays 3600. Conversion only.
Examples
Example 2
- 60 s
60
How many at 60? 60.
Example 3
- 86400 s
86400
How many at 86400? 86400. One day in seconds.
Related calculators
Common questions
How many seconds at TTL 3600?
3600. The entry stays seconds. Not dig.
What about 60?
60. One minute in seconds.
What about 86400?
86400. One day in seconds.
Does the calculator query a nameserver?
No. There is no live DNS. A number conversion only.
Is 3600 propagation time?
No. It is the TTL you type. Resolver cache is outside this calculator.
Does a comma in 3600,5 work?
Yes as a number. The examples keep 3600, 60, and 86400.
Does zero count?
Yes as 0 seconds. A blank field stops.
How is this different from DHCP range?
That card turns 192.168.1.0 /24 into 192.168.1.1. Here 3600 stays 3600.
Is 300 in the extras?
No. The three cards take 3600, 60, and 86400.
Knowledge sources
The calculator counts bits, bytes or throughput from your numbers. Below are SI and bit definitions (NIST).
Page updated in 2026.
What TTL controls
TTL (Time To Live) tells resolvers how long they may cache an answer (in seconds). It is not domain registration lifetime or a registrar “propagation deadline” — only a caching hint. This calculator converts seconds into minutes, hours, and days (e.g. 300 = 5 min, 86400 = 24 h).
Recursive resolver caching
- A resolver (ISP / 1.1.1.1 / 8.8.8.8) keeps the answer until TTL expires — different networks can see new and old IPs at the same time.
- Browsers and OSes also cache (hence “works for me, not for you”).
- NXDOMAIN has its own SOA timings — that also feels like “DNS won’t refresh.”
TTL quick-reference table
Common values at a glance. Form presets: 60, 300, 3600, 86400.
| Seconds | Minutes | Hours / days | Typical use |
|---|---|---|---|
| 60 | 1 | — | Tests, emergency cutover (more DNS queries) |
| 300 | 5 | — | Before migrations / failover |
| 600 | 10 | — | Short compromise when changes are frequent |
| 3600 | 60 | 1 h | Stable services — common default |
| 14400 | 240 | 4 h | Quieter DNS traffic, slower change |
| 86400 | 1440 | 24 h / 1 day | Rarely changed records; risky right before cutover |
Migration and delays
- Before cutover: lower TTL (e.g. 86400 → 300), wait ≥ the old TTL, then change the record; after things stabilize, raise TTL (e.g. 3600).
- Setting 300 today does not flush yesterday’s caches that still hold a 86400 TTL.
- If you still see the old IP: different resolver, OS/browser cache, CDN, or wrong record/zone — check with
dig @1.1.1.1.
A / AAAA / CNAME / MX scenarios
- A / AAAA — TTL sits directly on the IP. Web server move: short TTL → change IP → observe → longer TTL.
- CNAME — clients follow the target; both the CNAME TTL and the target record TTL matter. A short CNAME with a long target A can still “stick” on the old IP.
- MX — mail cutover: lower MX TTL (and related MX host A/AAAA) in advance; keep priorities coherent during the switch.
- Multiple NS / anycast — consistent publication on all NS; TTL will not fix a split zone.
Pre-change checklist
- Note the current TTL and convert it in the calculator.
- Lower to 300 (or 60 in an emergency), wait ≥ the previous TTL, change the record, verify on 2–3 resolvers.
- After things stabilize, raise TTL (e.g. 3600) and record real timings in the runbook.
Example: Monday 10:00 — 86400 → 300; Tuesday 10:00 — change A; Wednesday — raise to 3600.