This document guides you on how to delete a previously created public and private
DNS zone in Google Distributed Cloud (GDC) air-gapped, when it is empty and no longer
needed.
The intended audience for this document is
platform administrators and application operators responsible for managing DNS
records within a project.

## Before you begin

To delete DNS zones in GDC, you must have the following:

- An existing DNS zone to delete. See [List DNS zones](https://docs.cloud.google.com/distributed-cloud/hosted/docs/latest/gdcag/platform/pa-user/dns/list-dns-zones.md.txt) for guidance on listing your current zones.
- The necessary identity and access roles. To manage DNS records for your project, ask your **IAM Project Admin** to grant you the **Managed DNS Project Admin** (`managed-dns-project-admin`) role.
- To use the gdcloud CLI, ensure you have it installed. For more information, see [Install the gdcloud CLI](https://docs.cloud.google.com/distributed-cloud/hosted/docs/latest/gdcag/resources/gdcloud-install.md.txt).
- If you are using `kubectl`, a kubeconfig file for the global API server. If you have not yet generated this file, see [Sign in](https://docs.cloud.google.com/distributed-cloud/hosted/docs/latest/gdcag/platform/pa-user/iam/sign-in.md.txt#global-resources-kubeconfig). For more information, see [Global and zonal API servers](https://docs.cloud.google.com/distributed-cloud/hosted/docs/latest/gdcag/resources/multi-zone/api-servers.md.txt).

> [!CAUTION]
> **Caution:** Ensure that the DNS zone has no existing DNS records. You must delete all DNS records within a DNS zone before deleting the zone itself. Refer to [List DNS records](https://docs.cloud.google.com/distributed-cloud/hosted/docs/latest/gdcag/platform/pa-user/dns/list-dns-records.md.txt) and [Delete DNS records](https://docs.cloud.google.com/distributed-cloud/hosted/docs/latest/gdcag/platform/pa-user/dns/delete-dns-records.md.txt) to clear these records first.

## Delete a public or private DNS zone

You can delete a public or private DNS zone using the gdcloud CLI or the Kubernetes API.

### gdcloud

To delete a DNS zone, use the
[`gdcloud dns managed-zones delete`](https://docs.cloud.google.com/distributed-cloud/hosted/docs/latest/gdcag/resources/gdcloud-reference/gdcloud-dns-managed-zones-delete.md.txt)
command:

```bash
gdcloud dns managed-zones delete DNS_ZONE_NAME \
    [--project=PROJECT_NAMESPACE] \
    [--async]
```

Replace the following:

- `DNS_ZONE_NAME`: the name of your DNS zone to delete.
- `PROJECT_NAMESPACE`: the namespace of your project. This flag is optional if you have set a default project globally using `gdcloud config set project`.
- `--async`: Specify this if you want the command to return immediately, rather than wait for the operation to complete. You can use [`describe`](https://docs.cloud.google.com/distributed-cloud/hosted/docs/latest/gdcag/platform/pa-user/dns/list-dns-zones.md.txt#list-dns-zones) to check on the status of the operation.

### API

Use the Kubernetes API in GDC to delete a public or private DNS zone:

```yaml
kubectl --kubeconfig GLOBAL_API_SERVER \
delete manageddnszones.networking.global.gdc.goog/v1 DNS_ZONE_NAME \
-n PROJECT_NAMESPACE
```

Replace the following:

- `GLOBAL_API_SERVER`: the global API server's kubeconfig path. For more information, see [Global and zonal API servers](https://docs.cloud.google.com/distributed-cloud/hosted/docs/latest/gdcag/resources/multi-zone/api-servers.md.txt). If you have not yet generated a kubeconfig file for the API server, see [Sign in](https://docs.cloud.google.com/distributed-cloud/hosted/docs/latest/gdcag/platform/pa-user/iam/sign-in.md.txt) for details.
- `DNS_ZONE_NAME`: the name of your DNS zone which needs to be deleted.
- `PROJECT_NAMESPACE`: the namespace of your project.