Zone management and export

Create a zone

From Zones, choose Add Zone, select an organisation, enter the zone name, and review the SOA administrator email, remarks, and automatic-PTR setting. Choose Never, Always, or Only if domain exists according to whether A/AAAA records should create reverse DNS records. Saving creates a primary zone with managed SOA and NS records and opens its record list.

If the organisation has no available zone capacity, the form warns you and may create the zone disabled. A disabled zone does not serve its records. Review the organisation’s usage in Billing; free-tier eligibility and available capacity depend on the account and current subscription.

The platform supports common authoritative record types through the record editor. It does not currently expose a general BIND zone-file import in the web interface. See the migration guide for a verified move.

Understand zone status

The zone list’s status indicator means:

StatusMeaning
EnabledThe zone is enabled in echo reply and can serve its configured records
Disabledecho reply does not serve the zone. This may be a manual choice or a capacity safeguard

Some zones also show Waiting for nameserver change. This indicates a registrar-side nameserver update is pending or being verified. It is separate from the enabled/disabled state. Check the registered domain and the public parent delegation before assuming the change is complete.

This status is not a public-delegation check. Confirm which authoritative servers the parent publishes with dig NS your-domain.example +short and test the displayed nameservers directly.

Work with multiple zones and records

The zone list supports selecting zones for bulk actions such as enable, disable, edit, apply a template, export, or delete. Within a zone, select records to edit, enable or disable, move, or delete them. The action buttons available to you depend on your role. If your role cannot self-approve a change, saving submits it for review; it does not change live DNS until an authorised reviewer approves it. See team management for the role settings.

For reusable configurations, apply a DNS template from the zone’s record list. Review the resulting records before approval, especially when a template contains variables. See using templates.

If the zone is relayed from a DNS server you operate, see Private Masters. For query volume and DNS traffic breakdowns, see DNS query telemetry.

Export zones

Users with record-view permission can select one or more zones in Zones and choose Export:

  • one zone downloads as a BIND-format .zone text file
  • multiple zones download as a ZIP containing one zone file per zone

Keep an export before a migration or destructive change. An export is a recovery input, not a backup of registrar delegation, DS records, account permissions, billing, or registration state. Record those separately.

Delete a zone safely

Deletion permanently removes the zone’s DNS records from echo reply. Before deleting:

  1. export the zone
  2. verify that the domain is delegated to a working replacement, or intentionally no longer needs DNS
  3. account for DNSSEC DS records at the parent
  4. allow the delegation and relevant caches to move away from the old service

Deleting a zone does not change nameservers at an external registrar. If the zone is linked to a domain registered through echo reply, deletion also does not cancel that registration or its renewal handling. Manage the registration separately under Registered Domains.