dns.dnssec.complete-rollover

Finish a key-signing key rollover now, removing the old key

POST /dns/api/zones/{id}/dnssec/complete-rolloverIAM dns:CompleteDnssecKeyRolloverChanges stateDestructive

Only once the registrar has the new DS: a parent still pointing at the old key makes the zone fail validation.

Request syntax

POST /dns/api/zones/{id}/dnssec/complete-rollover

Path parameters

  • idRequired

    string

    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), the old key-signing key gone. 409 when no key-signing key rollover is under way; 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:CompleteDnssecKeyRollover 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 complete-rollover id

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_dns_dnssec_complete-rollover.