Skip to main content
POST
Enable DNSSEC

Authorizations

Authorization
string
header
required

Registrar API Bearer token. Obtain from dashboard at /dashboard/seller/api-access after requesting Registrar API access.

Path Parameters

domain_name
string
required

Domain name (e.g. example.com)

Body

application/json

DNSSEC key fields for enabling DNSSEC.

Atom / Parking nameservers: All fields are optional and will be ignored — DNSSEC is auto-managed.

Custom nameservers: flags, algorithm, protocol, and public_key are required. digest_type is optional (defaults to 2 / SHA-256).

flags
enum<integer>

DNSKEY flags. 256 = ZSK (Zone Signing Key), 257 = KSK (Key Signing Key). Ignored for Atom/Parking nameservers.

Available options:
256,
257
Example:

256

algorithm
enum<integer>

DNSKEY algorithm number. Ignored for Atom/Parking nameservers.

Available options:
3,
5,
6,
7,
8,
10,
12,
13,
14,
15,
16,
17,
23
Example:

13

protocol
enum<integer>

DNSKEY protocol. Must be 3 (the only valid value per RFC 4034). Ignored for Atom/Parking nameservers.

Available options:
3
Example:

3

public_key
string

Base64-encoded public key material from your DNS provider. Ignored for Atom/Parking nameservers.

Example:

"AwEAAaz/tAm8yeTHkmTpF84YtQQKDE2S..."

digest_type
enum<integer>
default:2

Digest algorithm used to compute the DS record returned in the response. Defaults to 2 (SHA-256). Ignored for Atom/Parking nameservers.

Available options:
1,
2,
3,
4
Example:

2

Response

DNSSEC enabled successfully

success
boolean
Example:

true

message
string
Example:

"DNSSEC enabled successfully"

data
object