Skip to content

Thalassa Cloud DNS

Thalassa Cloud DNS lets you manage the public names that point to your applications, load balancers, mail servers, and certificate checks — all from the same platform you use for compute and Kubernetes. Register a domain at your registrar, delegate it to Thalassa, then add the records your services need (for example www.example.com → your ingress IP, or a TXT record for Let’s Encrypt).

The pages below cover record types, import/export, DNSSEC, and API details when you need them.

Availability

DNS is available when the dns feature gate is enabled on your organisation. Contact your account team if DNS is not yet enabled for you.

Zones and records are managed through the console or the API at /v1/dns.

What you can do with DNS

CapabilityDescription
Host zonesDelegate domains to Thalassa-operated regional nameservers
Manage recordsA, AAAA, CNAME, NS, MX, TXT, CAA, and SRV RRsets
Import and exportMigrate zones with BIND-format zone files
Sign with DNSSECOptional zone signing using regional KMS asymmetric keys
Organisation or project scopeShared corporate domains or team-specific zones

Core concepts

ConceptDescription
DNS zoneA delegated domain. The zone name is the FQDN (for example example.com). Set at create time; it cannot be renamed afterwards.
DNS recordOne RRset in a zone, identified by name + type. Multiple values can live in a single record (for example two A records or several TXT strings).
Record nameRelative to the zone: @ (apex), * (wildcard), www, _acme-challenge, _sip._tcp, and so on.
Authoritative nameserversThalassa-operated nameservers in each cloud region. Delegate your domain at the registrar to these hostnames.
SOA recordManaged by the platform. Serial numbers are bumped automatically on every publish.

Documentation

Zone lifecycle overview

Create zone → Delegate NS at registrar → Add records → Publish to regional nameservers
                                                              │
                    Optional: Enable DNSSEC → Add DS at parent → Signed publish

See DNS zones for the full getting started workflow.

Related documentation