Step 1 · The pattern
Resolvers cache your record
Users do not ask your DNS server directly. They ask a resolver, which caches your record and reuses it until its TTL runs out. Each resolver has its own countdown.
- lookup
- right address
In short
TTL & slow rollbacks: how it works and how it breaks
Every DNS record carries a time-to-live, the number of seconds a resolver may keep the answer before asking again. A long TTL means fewer queries and protection if your DNS provider has trouble. It also means a change takes that long to reach everyone, and that applies to a rollback just as much. If you publish a wrong address with a 24-hour TTL and correct it five minutes later, any resolver that fetched the record in those five minutes will keep sending users to the wrong place until tomorrow. You cannot reach into other people's caches. The standard practice is to plan ahead. A day or two before a risky change, lower the TTL to a minute or so and wait for the old, long TTL to age out. Make the change. If it goes wrong, the fix spreads in a minute. Once things are stable, raise the TTL again.
How this comes up in interviews
"You pushed a wrong DNS record and corrected it five minutes later, yet some users are still broken hours on. Why, and what can you do?"
Then they ask
- How would you prepare the TTL for a risky DNS change planned for Friday?
- What do you give up by keeping a very short TTL all the time?
- During the change, why do different users get different answers?
A strong answer covers
- The TTL is how many seconds a resolver may keep an answer before asking again. Each resolver has its own countdown.
- A change spreads cache by cache, and a rollback is a change like any other.
- You cannot reach into other people's caches, so a mistake lives for up to the old TTL.
- Lower the TTL at least one old TTL before the change, so the long-lived copies have expired.
- Raise it again once stable: long TTLs mean fewer queries and protection if the provider has trouble.
Points to cover, not a script. Say them in your own words and tie them to a system you have worked on.
On one page: the track cheat sheet.
Sources: RFC 1035: Domain names, implementation and specification ↗ · Slack: What happened during Slack's DNSSEC rollout ↗ · RFC 9499: DNS terminology ↗ · Report a problem
Diagrams are our own simulations: the timings, rates and counts in them are illustrative, not measurements. Captions are original wording.