One-time downloads · $0.99 USD. No subscription.

Perunlight

Step-by-step guide

ZoneHandoff

Prepare a reviewable DNS handoff from two complete BIND exports, with exact original files and explicit record choices.

Use this when you have complete existing and proposed BIND exports for the same domain and need to agree what should change. It prepares local files for an operator to review. It does not query or change live DNS, establish provider completeness or test email delivery.

Get ZoneHandoff · $0.99

See it in use

Prepare a fictional DNS handoff

A screenshot walkthrough with fictional practice data. Select a step to explore.

1. Start with

Prepare a fictional DNS handoff

Brightfern has ten existing records, five proposed records and an expected candidate.

Sample files and contents

The free ZIP includes fictional existing.zone (10 records), proposed.zone (5 records) and expected-candidate.zone. Reserved .example names and documentation addresses are used; the mail strings are not deployable settings.

Practice files and guides are free. The complete app is included only where the product page says so.

2. In the app

Existing and proposed DNS records with their TTLs and explicit keep or replace choices.
Review complete record sets. Existing-only service records stay selected for preservation. Enlarge image ↗

Try it in three steps

  1. Load the example and choose the proposed apex address.
  2. Preserve omitted mail and CRM sets; adopt proposed SOA/NS together.
  3. Review the local draft and compare the expected candidate.
Show every click and setting
  1. Load the fictional example and choose the proposed apex A address, 198.51.100.20.
  2. Preserve the existing-only MX, SPF TXT, DMARC TXT, DKIM TXT and CRM CNAME; leave the existing www CNAME unchanged.
  3. Adopt the proposed SOA/NS together and complete the example review. Download the candidate handoff and save the project.
  4. Compare the expected candidate as a fresh export, then compare a copy with its MX line removed.

3. The result

Inspect the result

The in-app review keeps ten draft records in nine sets. It does not change live DNS; the free pack carries the expected candidate for comparison.

ZoneHandoff fictional Brightfern review with selected DNS record choices and required confirmations.
In-app Brightfern handoff review after record choices. The downloadable candidate remains a local draft and does not change live DNS. Enlarge image ↗
What to check in the practice result

A draft with 10 records in 9 RRsets, apex A 198.51.100.20, nameservers ns1.new.example. and ns2.new.example., and SOA serial 2026100202. Existing mail and CRM data remain. Original inputs are preserved byte for byte. Fresh comparison gives zero differences, or exactly one missing MX RRset after the MX line is removed.

The public free ZIP already contains expected-candidate.zone for the same fictional example; this image shows the in-app review.

See the workflow at a glance

Choose a short explanation, then follow the worked example below. Check the requirements and compatibility before using your own files.

A website change needs a service-record review.

A proposed website zone may omit records that other services still need. ZoneHandoff compares two complete supported BIND exports, preserves existing-only records by default and records your decisions in a draft handoff. The fictional Brightfern example changes the apex address while retaining five omitted mail and CRM service sets. You can then compare a fresh export against the candidate. This is local file preparation: it does not query or change DNS, certify email or prove that a provider export is complete.

View the illustrated card
A website change needs a service-record review. — the same explanation written above, with a labelled illustrative panel.
Download the full-size PNG card

Review omitted service records before accepting a web change

In the Brightfern example, the shorter proposed export is not a complete replacement plan. Make a separate decision for each service record set.

  1. The website address changes

    Choose the proposed apex address 198.51.100.20 while retaining the existing www choice shown in the example. Do not treat that web change as permission to remove unrelated services.

    Open the Brightfern comparison

  2. Mail and CRM are absent from the proposal

    Review and preserve the example’s MX, SPF, DMARC, DKIM and CRM record sets. For your own zone, confirm ownership and intent for each omitted set; an omission alone is not a deletion instruction.

    Resolve each record-set choice

  3. A candidate is ready

    Resolve every choice and adopt SOA/NS together as instructed. The example’s fresh candidate has zero differences, while removing MX leaves one missing record set. This checks exported records; it does not deploy DNS or test mail delivery.

    Check the verification boundary

Before you start

  • Extract the complete ZoneHandoff-1.0.1.zip. Workspace package 1.0.1 retains engine and saved-project schema 1.0.0. Linux Python 3.10.12 and Chrome 152 were checked. Live DNS/provider checks, BIND command validation, customer acceptance and other operating systems remain unverified.
  • Linux with Python 3.10+ and Chrome. Tested on Linux x86-64 with Python 3.10.12 and Chrome 152; other environments are unverified.
  • Extract the entire ZoneHandoff-1.0.1.zip. The parser is bundled: no pip install or internet connection is needed at runtime.
  • Complete UTF-8 BIND exports for one domain, including SOA and apex NS. Up to 2 MiB and 5,000 records per file; supported types only. Do not treat partial zone fragments as complete exports.

Your first result

  1. Extract and launch

    Extract the complete ZIP. Open a terminal in ZoneHandoff-1.0.0 and run python3 start.py. Use the printed http://127.0.0.1: address in Chrome if the browser does not open. Keep that terminal running. The local port can change on each launch.

  2. Try the fictional example

    Choose Load fictional example. You should see 10 existing records and 5 proposed records. For brightfern.example. A, choose Use proposed. Leave existing-only MX, SPF, DMARC, DKIM and CRM on Keep existing. The www CNAME stays unchanged.

  3. Resolve and review

    The example uses nameserver-move mode: in Review, confirm adoption of proposed SOA and NS together, read the limitations and record the provider-review action. Review the notice that www follows the changed apex. For real files, conduct the provider review with the operator; a checked box cannot prove completeness.

  4. Export and reopen

    Select Download candidate handoff, then Save project. Extract the handoff ZIP separately and open handoff.html to read, print or save as PDF. The ZIP contains original zone files, candidate.zone, decisions, a project and hashes. Later choose Reopen project to restore sources and decisions. A refused replacement leaves your current work and downloads unchanged. A successful reopen clears the previous fresh-export comparison; choose the matching fresh export and compare it again. Work is not autosaved.

  5. Compare a fresh export

    Under Fresh BIND export, select examples/expected-candidate.zone and click Compare fresh export: expect zero differences. Remove the MX line from a copy and compare again: expect exactly one missing MX RRset. This checks file parity, not running DNS or mail.

  6. Use your own files and close

    Enter your domain in ASCII/Punycode, choose complete existing and proposed exports and click Compare exports. Keep existing DNS is the default for your own files; choose a nameserver move only when intended. Changed inputs reset decisions. Save before closing, press Ctrl+C in the terminal and close the tab. To uninstall, delete the extracted folder; separately delete saved projects and exports you no longer need.

  7. Keep a file operation with the project that started it

    While a project or zone file is opening, the workspace pauses editing, examples, comparison and exports. Visible progress and error recovery prevent a delayed file from overwriting a newer project.

A worked example

Brightfern Studio: preserve five omitted service sets

Input: The free ZIP includes fictional existing.zone (10 records), proposed.zone (5 records) and expected-candidate.zone. Reserved .example names and documentation addresses are used; the mail strings are not deployable settings.

  1. Load the fictional example and choose the proposed apex A address, 198.51.100.20.
  2. Preserve the existing-only MX, SPF TXT, DMARC TXT, DKIM TXT and CRM CNAME; leave the existing www CNAME unchanged.
  3. Adopt the proposed SOA/NS together and complete the example review. Download the candidate handoff and save the project.
  4. Compare the expected candidate as a fresh export, then compare a copy with its MX line removed.

Expected result: A draft with 10 records in 9 RRsets, apex A 198.51.100.20, nameservers ns1.new.example. and ns2.new.example., and SOA serial 2026100202. Existing mail and CRM data remain. Original inputs are preserved byte for byte. Fresh comparison gives zero differences, or exactly one missing MX RRset after the MX line is removed.

Troubleshooting

Keep a file operation with the project that started it

While a project or zone file is opening, the workspace pauses editing, examples, comparison and exports. Visible progress and error recovery prevent a delayed file from overwriting a newer project.

Python is missing or the browser cannot connect

Use Python 3.10+ from your approved Linux software source. Launch from the extracted folder, keep the terminal open and use its current local address. Do not expose this local server to a network.

The source is refused

Read the refusal and obtain a supported complete export from the operator. Unsupported types, duplicate SOA, mixed TTLs, CNAME conflicts and provider markers are refused. Do not delete unsupported records just to pass validation.

Candidate download stays disabled

Resolve changed and new sets, required reasons, CNAME conflicts and review actions. An unresolved draft can be saved, but deliberately contains no candidate zone.

Reloading lost my choices

Use Reopen project with the last saved JSON. Unsaved work is held only in memory and cannot be recovered. Reimport originals if project hashes or decision identities no longer match.

A replacement project is refused

The selected project was not opened. Your current project, decisions and available downloads remain unchanged. Correct the reported problem or select a valid saved project, then reopen it.

Compatibility & limits

  • Accepts A, AAAA, CNAME, MX, TXT, SRV, CAA and apex NS/SOA in complete supported BIND exports. DNSSEC, delegations, wildcards, reverse zones, unknown types and provider metadata are excluded.
  • Conservative detection of ALIAS, ANAME, POOL, proxy, geoip and failover markers can refuse comments or quoted values. The app cannot detect provider features omitted from an export.
  • Local preparation only. No DNS query or change, provider import certification, propagation check, SPF evaluation or email test. Provider imports and environments other than the tested Linux/Chrome setup remain unverified.
  • Up to 2 MiB and 5,000 records per source; project request limit 8 MiB. Comments are retained in exact originals; candidate formatting is canonical. Comment review displays the first 500 comment-containing lines.
  • The candidate serial is a draft successor of the chosen snapshot. It does not establish live freshness. Original zone files are references, not immediately deployable rollback zones.
  • Projects and exports contain full zone records and notes. Share them only with the intended operators. The app has no automatic save, account, telemetry or cloud service.

Need a hand?

Tell us the product, host application and version, what you tried, and the exact error. Contact support with a fictional example; keep private customer files and passwords out of your message.