This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
Propagation is caches expiring. It is not a single worldwide switch. A resolver that cached the old answer will keep it until the TTL that was current when it cached it.
Lower the TTL before the change, and do that in an earlier window so caches can learn the short TTL. Changing the record and the TTL in the same minute does not speed up caches that already stored the old value.
The checker shows answers from resolvers you choose to ask about a name you operate. It does not force anyone to refresh. example.com is not your zone.
Write the old value, the new value, and the TTL you will wait for. Then stop looking every minute.
The change you can finish
Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.
Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.
- Read the current TTL.
- Write the old answer.
- If the TTL is long, plan an earlier window to shorten it.
- Change the record only in its own window.
- Wait the old TTL before judging the change.
- Do not flush resolvers you do not operate.
Mistakes that outlive the command
DNS Propagation Explained goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Judging a change before the old TTL.
- Shortening TTL and changing data together, then blaming the world.
- Asking resolvers about a zone you do not run, at volume.
- example.com left as the name.
Decisions to write down
One decision for DNS Propagation Explained: The TTL was read first. The old answer is written. The wait is the old TTL. And the name is your zone.
Checks before you call it done
Confirm this before you call the change done: TTL is in the ticket. Old and new values are written. The wait is explicit. No resolver you do not run was flushed. And the name is not example.com. If one of those fails, stop.
Wait the TTL you published.
example.com is not your zone.Before you leave the device
DNS Propagation Explained ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.
0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.
One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.
A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.