Rollback turns a recorded DNS change back into a draft changeset that reverses it. You review the proposed reverse, run validation, and apply it like any other changeset — never as an unreviewed direct write to your DNS provider.
Open any changeset in the Applied, Verified, or Propagated state and click Rollback. ZoneWatcher inverts every item in the original: a create becomes a delete, a delete becomes a re-create using the captured before-state, and an update flips its before- and after-state. The reverse lands in your changeset list as a Draft, ready to review and apply through the normal workflow.
Sometimes a change wasn't made through ZoneWatcher — somebody edited the zone directly at the provider, or a CI job pushed a record that shouldn't have shipped. ZoneWatcher's check history captures every change it observes, and modified checks expose a Revert Change action that drafts a changeset returning the zone to its state immediately before that check ran. Targeted to the records that changed, no more.
Rollbacks and reverts both produce drafts — never direct writes. The same dry-run validation, AI risk scoring, approval routing, and scheduling that protect a forward changeset also protect every rollback. If records have been deleted at the provider since the original change, the dry-run surfaces the missing records before you submit so you can adjust the draft.
DNS Change Rollback is included on the Control plan alongside Change Management. Start your free trial to try the full review-and-revert workflow on your own zones, or read the rollback guide for the complete behavior.
Start your free trial today and get full access to all monitoring features.