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
| Capability | Description |
|---|---|
| Host zones | Delegate domains to Thalassa-operated regional nameservers |
| Manage records | A, AAAA, CNAME, NS, MX, TXT, CAA, and SRV RRsets |
| Import and export | Migrate zones with BIND-format zone files |
| Sign with DNSSEC | Optional zone signing using regional KMS asymmetric keys |
| Organisation or project scope | Shared corporate domains or team-specific zones |
Core concepts
| Concept | Description |
|---|---|
| DNS zone | A delegated domain. The zone name is the FQDN (for example example.com). Set at create time; it cannot be renamed afterwards. |
| DNS record | One 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 name | Relative to the zone: @ (apex), * (wildcard), www, _acme-challenge, _sip._tcp, and so on. |
| Authoritative nameservers | Thalassa-operated nameservers in each cloud region. Delegate your domain at the registrar to these hostnames. |
| SOA record | Managed by the platform. Serial numbers are bumped automatically on every publish. |
Documentation
Create zones, delegate at your registrar, and manage records
Enable signing, DS delegation, and KMS key integration
IAM policies for zones and records
Endpoints and request requirements
Zone lifecycle overview
Create zone → Delegate NS at registrar → Add records → Publish to regional nameservers
│
Optional: Enable DNSSEC → Add DS at parent → Signed publishSee DNS zones for the full getting started workflow.
Related documentation
- Key Management Service (KMS) — Signing keys for DNSSEC
- KMS integrations — How DNSSEC uses KMS
- IAM policies — Project-scoped access control
- Projects — Organisation vs project resource scope
- API reference — Full platform API specification
- Regions — Regional deployment model