dns.dnssec.enableSign the zone (ECDSA P-256); returns the DS record for the registrar
The zone is signed within one nameserver pull. Validation starts once the DS is at the registrar.
Request syntax
POST /dns/api/zones/{id}/dnssec/enablePath parameters
idRequiredstring
Constraints: uuid
Response
200 with the DNSSEC view: status (off, signing or disabling), available (false without the installation key), algorithm, ds (the DS records for the registrar, one per active key-signing key), keys (id, role, state, keyTag, ds, activateAfter, removeAfter, …), parentDs and parentCheckedAt (what the parent served at the last check), disableAfter, and secure (the parent serves a DS of an active key-signing key); status is signing and ds holds the record for the registrar. 409 when the installation has no DNSSEC key-sealing key; 404 when the organization has no such zone.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow dns:EnableDnssec on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud dns dnssec enable idcurl -X POST "https://console.platform-development.deutschecloud.app/dns/api/zones/id/dnssec/enable" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_dns_dnssec_enable.