Online Tool Store Online Tool Store

DNS TTL Planner

Enter your event type and current TTL to get a step-by-step timeline for lowering and restoring DNS TTL safely. Runs entirely in your browser.

🔒 This tool runs entirely in your browser. Your files are never uploaded to a server.

Recommended plan

1. Lower TTL to 300s 24 hours before the change
2. Make the DNS change once old TTL has expired
3. Restore TTL to 86400s after confirming propagation

Example shown — replace it with your own current TTL and event.

How it works

  1. Choose the type of DNS change you're planning.
  2. Enter your record's current TTL.
  3. Get a step-by-step timeline for lowering and restoring TTL safely.

Planning calculates how long before your change to lower the TTL — based on the current TTL value — so old cached records expire everywhere before you make the real change, minimizing propagation delay and downtime risk.

FAQ

Is my DNS data uploaded anywhere?

No. Planning happens entirely in your browser — nothing is sent to a server.

What is DNS TTL?

Time to live — how long, in seconds, resolvers are allowed to cache a DNS record before checking for updates again.

Why lower TTL before a planned change?

A lower TTL means resolvers check for updates sooner, so once you make the actual change, it propagates faster — minimizing the window where some visitors see stale records.

How long before the change should I lower the TTL?

At least as long as your current TTL, so the old, longer-cached value has fully expired everywhere before you make the real change.

How we compare

Feature Online Tool Store Doing the math by hand DNS provider dashboards
Step-by-step timeline includedEasy to mistimeOnly manages the record, not the timing plan
Free, no accountRequires a DNS provider account

A DNS dashboard changes the record but doesn't plan the timing. DNS TTL Planner gives you the exact schedule to minimize downtime.

Explore related tools

Embed this tool

Paste this on your own site — it stays free, and every file still stays in your visitor's browser, not yours or ours.