Skip to main content
POST
Declare a custom DNS zone on the cluster

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

x-ankra-organisation-id
string

PAT organisation override.

Path Parameters

cluster_id
string<uuid4>
required

Body

application/json
credential_name
string
required
zone
string
required
provider
enum<string>

Optional. Which kind of credential credential_name must be: 'cloudflare', 'webhook' or 'avura'. A mismatch is refused (400). With 'cloudflare', or whenever the name resolves to a Cloudflare credential, Ankra first checks with Cloudflare that the token reaches the zone with DNS edit.

Available options:
cloudflare,
webhook,
avura

Response

The stored, normalised binding

success
boolean
required
zone
string
required
credential_name
string
provider
string | null

Declare only: how the zone is published ('cloudflare', 'webhook' or 'avura').

policy
string | null

Declare only: the external-dns policy the zone's controller runs ('upsert-only' for Cloudflare, 'sync' otherwise).

cloudflare_zone
string

Declare of a Cloudflare-bound zone only: the Cloudflare zone the records land in (the declared zone or the nearest ancestor zone).

dns_edit_access
enum<string>

Declare of a Cloudflare-bound zone only: 'granted' when Cloudflare listed DNS edit for the token on the zone, 'unknown' when Cloudflare did not report the token's permissions.

Available options:
granted,
unknown