> 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/secondary-zone/view-secondary-zone-details.md).
# View Secondary Zone Details
IONOS Cloud DNS: view details of a secondary 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 secondary zones. You can set user privileges in the [DCD](/cloud/network-services/cloud-dns/dcd-how-tos/set-user-privileges.md) or using the [API](/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 **Secondary Zones** from the drop-down list.
{% hint style="info" %}
**Info:** The **Public zones** section displays the zones if you have already created them. Select **Show secondary zones** to view secondary zones. This option only appears if you have created secondary zones but have not configured primary zones.
{% endhint %}
3\. Select the zone to view its details. You can either click on the zone name or select **Details & Records** from the **ACTIONS** column.
{% hint style="success" %}
**Result:** The following information is displayed in the **Details & Records** window:
* **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.
* **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.
* **Primary IPs:** Displays the primary IP addresses that is associated with the respective secondary 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.
* Select
* [Start zone transfer](/cloud/network-services/cloud-dns/dcd-how-tos/public-zone/secondary-zone/start-zone-transfer.md) to initiate manual zone transfer.
* [Edit zone](/cloud/network-services/cloud-dns/dcd-how-tos/public-zone/secondary-zone/update-secondary-zone.md) to update zone details.
* The zone records transferred from the primary zone are listed. You can view the FQDN, record type, content, whether it is enabled or disabled, and view record details.
{% endhint %}
---
# 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/secondary-zone/view-secondary-zone-details.md?ask=&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.