Cancel pending DNSSEC transition
POST /dns/{domain}/dnssec/cancelOperation ID: CancelDNSSECByDomain
Cancel a currently pending DNSSEC activation or, for regfish-managed nameservers, a pending DNSSEC deactivation.
If no cancellable transition exists, the request fails with 409.
Path parameters
Section titled “Path parameters”| Name | Type | Required | Description |
|---|---|---|---|
domain |
fqdn_relaxed | yes | — |
Responses
Section titled “Responses”| Status | Type | Description |
|---|---|---|
200 |
dnssecResponse |
DNSSEC transition cancelled or current stable state returned |
401 |
Error |
Unauthorized |
404 |
Error |
Domain not found |
409 |
Error |
No cancellable DNSSEC transition exists for this domain or the current transition cannot be rolled back automatically |
Response body
Section titled “Response body”| Field | Type | Required | Description |
|---|---|---|---|
success |
boolean |
yes | Success indicator |
code |
integer |
no | Response/Error Code |
response |
dnssecResponse | no | — |
Example
Section titled “Example”curl -X POST "https://api.regfish.com/dns/<domain>/dnssec/cancel" \ -H "x-api-key: $REGFISH_API_KEY"Build a request
Section titled “Build a request”Fill in values — the call below updates as you type. Nothing is sent: the API does not currently allow browser requests from this domain (CORS). The API key is not stored.