← Back to all tools

DNS Propagation Planner

Model TTL-lowering lead time, resolver cache cohorts, and conservative record-change visibility windows.

Migration inputs

Current TTL (seconds)

Reduced TTL (seconds)

Display timezoneUTCBrowser local timezone

TTL lowered at

Planned record change

Negative TTL (seconds)

Include a prior NXDOMAIN/negative-cache cohort

Optional resolver lookup timesMaximum 100; timestamps must include Z or a numeric UTC offset.

Build migration planReset

Assumptions: An authoritative TTL change is immediately available and a resolver that queries just before an event may retain its answer for the entire applicable TTL. The conservative pre-lowering cohort expires at “TTL lowered + current TTL”; a cache refreshed just before cutover expires at “record change + reduced TTL.” The optional negative cohort uses the supplied effective negative TTL. Resolver TTL floors/caps, prefetch, forwarding layers, DNS provider delays, clock skew, serve-stale behavior, record-specific behavior, failures, and client/application caches are not modeled. DNS propagation cannot be guaranteed from TTL arithmetic alone.