> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/network-services/cloud-dns/dcd-how-tos/public-zone/primary-zone/view-primary-zone-details.md).

# View Primary Zone Details

IONOS Cloud DNS: view details of a primary DNS zone using the DCD

{% hint style="info" %}
**Prerequisite:** Only contract administrators, owners, and users with **Access and manage DNS** privilege can create and manage primary zones and records. You can set user privileges in the [<mark style="color:blue;">DCD</mark>](/cloud/network-services/cloud-dns/dcd-how-tos/set-user-privileges.md) or the [<mark style="color:blue;">API</mark>](/cloud/network-services/cloud-dns/api-how-tos/set-user-privileges-api.md).
{% endhint %}

To view details of a given zone, follow these steps:

1\. In the **DCD**, go to **Menu** > **Network Services** > **Cloud DNS** > **Public zones** tab.

2\. Select **Primary Zones** from the drop-down list.

3\. Select the zone to view its details. Alternatively, you can also select **Details & Records** in the **ACTION** column to view the details.

![Zone selection](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-85b510ea4adb54496925ce3dbaebb38f8505ebfe%2Fzones-overview.png?alt=media)

4\. In the **Details & Records** window, select **Zone details**. To update the zone details, click [<mark style="color:blue;">Edit zone</mark>](/cloud/network-services/cloud-dns/dcd-how-tos/public-zone/primary-zone/update-primary-zone.md).

{% hint style="success" %}
**Result:** The following information is displayed in **Zone details**:

* **Zone Name:** Displays the name of the zone.
* **State:** Indicates if the zone is **Available**.
  * **Available:** Indicates that the zone is available and healthy.
  * **Provisioning:** Indicates that the zone is being created or updated.
  * **Destroying:** Indicates that the zone is being deleted.
  * **Failed:** Indicates that an error occurred during creation, update or deletion.
* **Enabled:** Displays **Yes** if the zone is **Enabled** or **No** when it is **Disabled**.
* **UUID:** Displays the UUID of the zone. Click **Copy** if you want to copy it to the clipboard.
* **Creation date:** Displays the creation date and time of the zone.
* **Last modified:** Displays the last modified date and time of the zone.
* **Nameservers:** Displays the nameservers of the zone. Click **Copy** if you want to copy it to the clipboard.
* **Description:** Displays the description of the zone.
  {% endhint %}

![Zone details](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-29c95c95b834431bb6301f850d0d4e4227d539b1%2Fzone-details.png?alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ionos.com/cloud/network-services/cloud-dns/dcd-how-tos/public-zone/primary-zone/view-primary-zone-details.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
