Deleting a DNS zone through Domain Nexus can affect the remote authoritative service. It is not merely hiding a local list entry. Recovery uses retained zone evidence and the supported provider workflow, so prepare a backup and dependency review before deletion.
IN THIS ARTICLE
01 Delete an authorised zone
| Method | Resource | Scope | Idempotency-Key |
|---|---|---|---|
DELETE |
/v2/dns/zones/{zoneId} |
dns:delete |
Required |
POST |
/v2/dns/zones/{zoneId}/restore |
dns:delete |
Required |
- Read the zone and confirm its exact name, owner, provider bindings and current service use.
- Export the records and verify a completed backup if your package supports it.
- Check website, mail, verification, reverse-DNS and forwarding dependencies. Ensure the domain's public delegation will not continue relying on a zone you are about to remove.
- Submit the DELETE request with the required idempotency key after the owner approves that DNS action.
- Inspect the returned result and any provider tasks. Verify the final management and authoritative state.
02 Recover through retained-zone restore
When a deleted zone remains eligible for recovery, POST to its restore route using the original owned zone reference. The service checks retained evidence, ownership and provider availability. Follow the result, then compare restored records and provider bindings before returning the domain to service.
Will restore renew an expired registration?
No. DNS-zone restoration and domain renewal or redemption are different operations. An active DNS zone does not make an expired or deleted registration usable. Review the domain's registry lifecycle separately.
Is restoration guaranteed?
No. It depends on retained data and the current provider and ownership conditions. A downloaded export is useful independent evidence, but may not contain provider-specific features or signing keys. Keep an operational backup plan rather than relying on indefinite trash retention.
If deletion was uncertain, do not immediately create a second zone of the same name. Reconcile the original provider state and the retained resource first. Likewise, do not edit the module database to mark a failed deletion complete: that can leave a live remote zone with no accurate management record. Preserve the request and task references for the authorised recovery review.
Related articles
- Request, list and download DNS backups through the API
- Approve a current backup restore preview before changing DNS
- Request registry deletion without confusing it with DNS-zone removal
- Why deleting a DNS zone does not cancel or release the domain registration
- Refresh a secondary DNS zone and interpret its task state