Small DNS habits that reduce surprises

Useful habits

• Record old and new values.
• Write down the expected TTL behavior.
• Keep the exact verification command with the change note.

Record the before state

DNS changes are hard to review when the old value disappears from memory. Write the previous value, the new value, and the reason for the change before editing the record.

This is not extra paperwork. It is the easiest way to answer what changed if the result is mixed later.

Keep TTL expectations realistic

TTL behavior can make DNS feel inconsistent. The note should say what TTL is expected and when a later check should be meaningful.

That makes it easier to distinguish normal propagation delay from a real mistake.

Store the check beside the change

The exact command or resolver used for verification should stay in the note. A future reviewer can repeat the same check before trying a different one.

This habit is especially useful when multiple people make DNS changes for the same small site.

DNS habit checklist

• Write old value, new value, and reason.
• Record expected TTL behavior.
• Check from a public resolver.
• Open the page that depends on the record.
• Keep the verification command in the note.