Skip to content
API reference

DNS API reference

The DNS API is part of the Thalassa Cloud platform API. Full OpenAPI definitions are available in the API reference.

Base path

/v1/dns

Required headers

HeaderRequiredDescription
AuthorizationYesBearer token or equivalent credential
X-Organisation-IdentityYesOrganisation identifier
X-Project-IdentityNoProject identifier for project-scoped zones

Endpoints

MethodEndpointDescription
GET/v1/dns/zonesList DNS zones
POST/v1/dns/zonesCreate a zone
GET/v1/dns/zones/{zone}Get zone details
DELETE/v1/dns/zones/{zone}Delete a zone and all records
GET/v1/dns/zones/{zone}/exportExport zone as BIND format
POST/v1/dns/zones/{zone}/importImport BIND zone file (merge or replace)
GET/v1/dns/zones/{zone}/recordsList records in a zone
POST/v1/dns/zones/{zone}/recordsCreate a record
GET/v1/dns/zones/{zone}/records/{name}/{type}Get a record
PATCH/v1/dns/zones/{zone}/records/{name}/{type}Update TTL or values
DELETE/v1/dns/zones/{zone}/records/{name}/{type}Delete a record
GET/v1/dns/zones/{zone}/dnssecGet DNSSEC status and DS records
PUT/v1/dns/zones/{zone}/dnssecEnable or update DNSSEC signing
DELETE/v1/dns/zones/{zone}/dnssecDisable DNSSEC signing

Replace {zone} with the zone name (FQDN), {name} with the record name relative to the zone, and {type} with the record type (for example A, MX, TXT).

Import behaviour

When importing a BIND zone file via POST /v1/dns/zones/{zone}/import:

OptionBehaviour
Default (merge)Records in the file are created or updated; existing records not in the file are unchanged
replaceExisting: trueDeletes records in the zone that are not present in the imported file

Supported record types in imports: A, AAAA, CNAME, NS, MX, TXT, CAA, SRV. SOA, PTR, DS, and other types are skipped.

Publishing

Record create, update, and delete operations trigger a full zone file publish to regional authoritative nameservers. Expect updated answers within roughly 25–40 seconds. See How publishing works for details.

Feature gates

Feature gateRequired for
dnsAll DNS API operations
kmsDNSSEC enable, update, and status (in addition to dns)

If a feature gate is disabled, affected calls return 403 Forbidden.

Related documentation

  • DNS zones — Record types, TTL rules, and examples
  • DNSSEC — Signing configuration and status fields
  • Access control — IAM resources and built-in policies