List DNSSEC records
GET /api/v2/domains/{id}/dnssec
Lists the DNSSEC records the registry holds for the domain. The response also shows the record type the registry takes (recordType), the algorithms and digest types it accepts and whether records can be added or removed (actions). Use it to manage manual DS/KEY records, for a domain whose DNS is signed by another provider. Domains on Hostup nameservers normally get their DS record from automatic DNSSEC (GET /api/v2/domains/{id}/dnssec-auto). When the registry holds no DNSSEC record but the zone is already signed, detectedRecords holds the record that completes the chain. Send its values to POST /api/v2/domains/{id}/dnssec to turn DNSSEC on. While a .se or .nu registry lock is on, actions denies both changes and gives the reason.
Authentication: An API key with the scope read:domains. About keys and scopes
Request
Path parameters
idstringrequireddom_…).Example
curl "https://cloud.hostup.se/api/v2/domains/dom_01hxa3b4c5d6e7f8g9h0j1k2m3/dnssec" \ -H "Authorization: Bearer $HOSTUP_API_KEY"Responses
200 The domain’s DNSSEC records, the accepted formats and the action gates.
{ "domainName": "example.se", "recordType": "DS", "dsRecords": [ { "id": "dsr_01hxa3b4c5d6e7f8g9h0j1k2m3", "keyTag": "2371", "algorithm": "13", "digestType": "2", "digest": "5A1D7C1B9E7F4E6A8C2B0D5F9A3E6C7D8B1A2C3D4E5F60718293A4B5C6D7E8F9" } ], "keyRecords": [], "allowedAlgorithms": [ 8, 10, 12, 13, 14 ], "allowedDigestTypes": [ 2, 3, 4 ], "algorithmNames": { "1": "RSA/MD5", "2": "Diffie-Hellman", "3": "DSA/SHA-1", "5": "RSA/SHA-1", "6": "DSA-NSEC3-SHA1", "7": "RSASHA1-NSEC3-SHA1", "8": "RSA/SHA-256", "10": "RSA/SHA-512", "12": "GOST R 34.10-2001", "13": "ECDSA Curve P-256 with SHA-256", "14": "ECDSA Curve P-384 with SHA-384", "15": "Ed25519", "16": "Ed448" }, "digestTypeNames": { "1": "SHA-1", "2": "SHA-256", "3": "GOST R 34.11-94", "4": "SHA-384" }, "status": "active", "reason": null, "actions": { "canAdd": { "allowed": true, "reason": null }, "canRemove": { "allowed": true, "reason": null } }, "detectedRecords": []}Response fields
domainNamestring | nullrecordTypestringDS or KEY. One of DS, KEY.dsRecordsarray of objectidstring | nulldsr_…). Use it to delete the record.keyTagstring | nullalgorithmstring | nulldigestTypestring | nulldigeststring | nullkeyRecordsarray of objectidstring | nulldsr_…). Use it to delete the record.flagstring | nullprotocolstring | nullalgorithmstring | nullpublicKeystring | nullallowedAlgorithmsarray of integerallowedDigestTypesarray of integeralgorithmNamesobjectdigestTypeNamesobjectstatusstringactive (records can be managed), unsupported (DNSSEC is not available for this domain, see reason) or error (the registry data could not be read, try again later). One of active, unsupported, error.reasonstring | nullstatus is unsupported or error. Null when active.actionsobjectcanAddobjectallowedbooleanreasonstring | nullcanRemoveobjectallowedbooleanreasonstring | nulldetectedRecordsarray of objectPOST /api/v2/domains/{id}/dnssec returns.recordTypestringDS or KEY, matching recordType. One of DS, KEY.dsobject | nullidstring | nulldsr_…). Null until the record is at the registry.keyTagstring | nullalgorithmstring | nulldigestTypestring | nulldigeststring | nullkeyobject | nullidstring | nulldsr_…). Null until the record is at the registry.flagstring | nullprotocolstring | nullalgorithmstring | nullpublicKeystring | nullErrors
Errors are Problem Details with a stable code. Branch on the code, not on the text.
| 400 | Invalid request. The response body is an RFC 7807 Problem Details document. |
| 401 | Unauthorized. Authentication is required. |
| 403 | Forbidden. The caller lacks a required scope or does not own the resource. |
| 404 | Not found. The resource does not exist or is not owned by the caller; code is domain_not_found. |
| 429 | Rate limited. Retry after the limit resets. 429 responses include Retry-After seconds plus X-RateLimit-* headers. |
| 500 | Internal error. Retry later or contact support if the issue persists. |
| 502 | Upstream failure. A dependent provider request failed; the Problem Details code is upstream_failed. Retry later or contact support if the issue persists. |