DNS TTL Converter

Accepts a number of seconds (3600) or a BIND-style duration (1h, 30m, 1h30m, 1d12h, 1w). The maximum allowed value is 2,147,483,647 seconds (RFC 2181).

What this TTL range is typically used for

• Migration / launch30 seconds to 5 minutes

  Use right before a planned change so resolvers expire cached records quickly. Increases query load on your authoritative servers, so raise it back up after the change settles.

• Short / dynamic5 minutes to 30 minutes

  Suitable for failover endpoints, blue/green deployments, and records you may need to repoint with limited notice. A reasonable balance between propagation speed and DNS load.

• Balanced default30 minutes to 4 hoursCurrent

  The default range many DNS providers ship with (Cloudflare Auto, Route 53 default, GoDaddy default). Records propagate within a working session and query volume stays modest.

• Stable production4 hours to 1 day

  Best for A, AAAA, and CNAME records that change rarely. Resolvers and CDNs can cache aggressively, lowering query load and improving cache hit rates worldwide.

• Very long1 day or more

  Common for MX, NS, SOA, and TXT records that almost never change. Resolvers may hold the value for the full TTL, so any change needs at least that much lead time before it is universally honored.

Notes on DNS TTL behavior

• RFC 2181: the TTL is a 32-bit unsigned integer in seconds. Values above 2^31 - 1 SHOULD be treated as zero by resolvers.
• Negative caching: SOA records carry a separate minimum TTL used for caching NXDOMAIN responses. This converter handles record TTLs, not negative cache.
• Authority vs resolver: the TTL you set is the maximum a downstream resolver should cache the answer. Resolvers may serve a shorter cached copy, but they will not exceed your value.
• BIND notation: 1w = 1 week, 1d = 1 day, 1h = 1 hour, 1m = 1 minute, 1s = 1 second. Combine tokens in any order, each at most once: 1d12h is valid, 1d12h30m is valid, 1h2h is not.
• Provider UIs vary: Cloudflare exposes Auto plus 1 min through 1 day, Route 53 defaults to 300 seconds, GoDaddy defaults to 1 hour. The value on the wire is always plain seconds regardless of how the UI displays it.
• Local only: nothing you type is uploaded. All math runs in the browser.