> 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/tools-terraform/docs/data-sources/dns_zone_dnssec.md).

# ionoscloud\_dns\_zone\_dnssec

Get the DNSSEC key information of a DNS Zone.

Reads the DNSSEC signing key of a DNS Zone, including the values needed for the DS record. Fails if DNSSEC is not enabled for the zone.

> ⚠️ Only tokens are accepted for authorization in the **ionoscloud\_dns\_zone\_dnssec** data source. Please ensure you are using tokens as other methods will not be valid.

## Example Usage

```hcl
data "ionoscloud_dns_zone_dnssec" "example" {
  zone_id = "zone_id"
}

output "ds_record" {
  value = data.ionoscloud_dns_zone_dnssec.example.ds_record
}
```

## Argument reference

* `zone_id` - (Required)\[string] The ID (UUID) of the DNS zone.

## Attributes reference

* `id` - The ID of the data source, equal to `zone_id`.
* `algorithm` - The signing algorithm.
* `nsec_mode` - The authenticated denial of existence mode.
* `ds_record` - The DS record to hand over to the registrar, formatted as `<key_tag> <algorithm_number> <digest_type> <digest>`.
* `key_tag` - The key tag of the zone signing key.
* `algorithm_number` - The IANA DNS Security Algorithm Number.
* `digest_type` - The IANA DS digest type number.
* `digest_algorithm_mnemonic` - The mnemonic of the digest algorithm.
* `digest` - The digest of the DNSKEY.
* `flags` - The flags of the DNSKEY record.
* `public_key` - The Base64 encoded public key of the DNSKEY record.
* `composed_key_data` - The DNSKEY RDATA: flags, protocol, algorithm and public key.


---

# 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/tools-terraform/docs/data-sources/dns_zone_dnssec.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.