DNS Service
Give every deployment a working domain — use a free Studio-managed subdomain, connect your own DNS provider, or point records yourself with the manual flow.
Every service you deploy gets its own public address (see Deploying Services). The DNS Service is what makes those addresses resolve. You choose how domains are supplied when you set up a cluster, and Studio handles the rest.
How DNS Works in Studio
There are three paths, and you pick one per cluster:
- Free Studio-managed subdomain — the simplest option. Studio hosts the subdomain for you, so deployments get a working address with nothing to configure on your side.
- Your own DNS provider — bring a domain you own at a supported provider. Studio manages the records for you as deployments come and go.
- Manual (DIY) domain — you keep full control and point the records yourself.
Whichever path you choose, each deployment still gets its own subdomain and TLS certificate automatically.
Supported DNS Hosts
If you bring your own domain, Studio can manage records for you automatically when your domain is hosted at one of these providers:
- AWS Route 53
- Cloudflare DNS
- Google Cloud DNS
- Azure DNS
- RFC2136 (standards-based dynamic DNS)
Select your provider during cluster setup and supply the credentials it needs. Studio then creates and updates the records for your deployments without further steps from you.
Bring Your Own DNS (DIY)
If your domain is hosted somewhere Studio doesn't manage directly — or you simply prefer to keep control — choose the manual (DIY) option. Studio records your real domain name and tells you exactly what to set:
Choose the manual / DIY domain option and enter the domain you want to use.
Note the cluster's public IP that Studio shows you.
In your own DNS host, point a wildcard record for your domain at that IP, so every deployment subdomain resolves to the cluster.
With DIY, Studio doesn't touch your DNS host — it only tells you the record to create. Managing and renewing records is up to you, while TLS certificates are still issued automatically once the record resolves.
Migrating Existing Records
If you already run DNS for a domain and want to bring it into Studio:
- Moving to your own provider path — connect the provider during cluster setup. Existing records you manage by hand stay as they are; Studio only adds and updates the subdomain records for your deployments.
- Moving to the DIY path — add the wildcard record pointing at the cluster IP alongside your existing records. Your current entries keep working; only new deployment subdomains flow through the wildcard.
- Switching to a free Studio subdomain — your deployments move to the managed subdomain. Any records under your old domain remain yours to keep or retire.
Point a wildcard record at the cluster only after the cluster is up and you know its public IP. Records that resolve to an address before the cluster is ready will fail until the cluster answers on ports 80 and 443.