Time Machine

Every change to a zone stores a complete copy of it, not a diff. You can compare any two points in time and restore the one that worked.

Included on paid plans, with the history window set by your plan — 7 days on Starter, 14 on Growth, 30 on Business, 90 on Enterprise. Not on free.

Why whole copies matter

A diff tells you what changed. A whole copy tells you what the zone was — which is the question you are actually asking at 2am, when you do not yet know which change broke it and cannot trust your memory of what the zone looked like yesterday.

It also means a restore is one step rather than an unwind of several.

Comparing

Pick two versions and the portal shows what moved between them: records added, removed and changed. This is usually enough to identify the culprit without restoring anything, which is the better outcome — a targeted fix beats reverting three days of legitimate work.

Restoring

Restoring makes the zone match that version, and publishes it. Records added after that point are removed; records deleted after it come back.

Read the comparison before you restore. If good changes were made after the bad one, restoring throws them away too. In that case fix the specific record instead, and use the version view as a reference for what it should say.

A restore is itself a change, so it creates a version of its own. You can undo an undo.

What it does not cover

Time Machine is per zone. It does not restore a deleted zone — that is the recycle bin — and it holds nothing about your account, plan or billing.

Last reviewed 2026-08-19.