# Domain Revocation (Destruction)

Any existing ZNS domain can be revoked at any time by its canonical owner -- i.e., the owner of the record in `ZNSRegistry`. Fundamentally speaking, domain revocation is equivalent to destroying the domain: ownership is forfeited, the domain record in `ZNSRegistry` is deleted, the associated NFT token is burned, and the domain becomes available again for anybody to register. In the event that a revoked domain was registered via ZERO's stake-to-mint paradigm, the amount of the stake will be refunded (minus the small protocol fee), though payments made at the time of registration for fees and transaction costs will not be refunded. This is true event for domains purchased on secondary or transferred; the new owner of the domain will inherit that domain's stake (if it was registered via stake-to-mint) and will be able to reclaim that stake in full via the revocation process.

<figure><img src="/files/DKOKwAFCl94mS3BH7Qqi" alt=""><figcaption><p>The core domain revocation flow</p></figcaption></figure>

> Upon revocation of a domain registered via stake-to-mint, the original stake amount is refunded to the domain's owner -- regardless of whether they were the original owner -- excluding the applicable fees paid at time of mint.

In the event that a revoked domain has existing subdomains underneath it, those child domains remain emancipated and unaffected by their parent domain's revocation. Still, no new subdomains can be minted under a revoked domain until it has been registered anew. In the interim, the revoked domain's hash is assigned the access type `Locked`*,* as shown above illustration. When a new domain is minted with the same name as the revoked domain, the new owner will be able to reset the access type and any other data associated with the domain configuration. Owners of a new domain that had been previously revoked do have the ability to set any of price or payment configuration variables, but this does not affect the ability of existing subdomains to revoke correctly if that was how they was configured when they registered initially under the previous incarnation of their parent domain.

When a new domain is minted with the same name as a previously revoked domain, it will inherit existing subdomains and those domains will be viewed as child domains by ZNS. This is as an artifact of having the same domain name -- and thus domain name hash, see [Names and Hashing](/zns/names-and-hashing.md) -- as the previously revoked domain.

{% hint style="warning" %}

* To revoke a domain, a user must own the record in `ZNSRegistry` (canonical owner).
* Domain revocation will ALWAYS burn the domain token REGARDLESS of which account the token belongs to at the time of revocation.
  * If you own the token on a different account, it is not necessary to move it to a the canonical owner address to revoke.
  * If you are not the canonical owner, but have domain token in your account at the time of revocation, this will burn the token without your knowledge or participation.
    {% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://zer0-1.gitbook.io/zns/domain-management/domain-revocation-destruction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.