Guides
Guides for adding custom domains to a multi-tenant app, for adding DNS records at each provider, and for how one-click setup works.
The guides go deeper than the reference pages. Some are for the developer wiring DoDomain into a product; some are for the person adding DNS records at a registrar. This page links every one of them, so it is the place to start whether you are reading or an agent is crawling.
How to pick one:
- You build a multi-tenant product and customers want
app.theirdomain.com: read the framework guide for your stack. - Someone has to add DNS records at a specific provider: open that provider's guide, or send it to them.
- You want to know why one-click setup works at some providers and not others: read the Domain Connect field notes.
- You have not integrated yet: start with Getting started.
Framework guides
Each one covers the same four problems in the idioms of the framework: resolve the tenant from the request host, mint and verify the DNS records, receive the signed webhook, and place TLS.
- Custom domains in multi-tenant Next.js
- Custom domains for a multi-tenant Rails app
- Custom domains in multi-tenant Laravel
- Custom domains for a multi-tenant Django app
DNS provider guides
One page per provider, with the vocabulary of that provider's own DNS panel: where the records live, what goes in the host field, and how to check the record is live. The DNS provider setup guides hub has the same list with the root-domain entry and the date each guide was checked.
- AWS Route 53
- Bluehost
- Cloudflare
- DigitalOcean
- DNSimple
- Domain Chief
- DreamHost
- Dynadot
- Enom
- Gandi
- Glauca HexDNS
- GoDaddy
- Google Cloud DNS
- HostGator
- Hostinger
- Hover
- Infomaniak
- IONOS
- Name.com
- Namecheap
- NameSilo
- Network Solutions
- one.com
- OVHcloud
- Porkbun
- Simply.com
- Squarespace Domains
- STRATO
- TransIP
- Vercel
- Wix
- WordPress.com
Domain Connect
Domain Connect field notes: every bug we hit is the engineering write-up of shipping signed, one-click DNS applies over the open protocol: the template registry, the gaps in the spec, the provider bugs, and why a probe that answers 200 proves nothing.
Where to go next
- Getting started: from signup to a verified custom domain.
- REST API: authentication, every endpoint, the errors and the webhooks.
- FAQ: short answers to the questions integrators ask most.
FAQ
The questions integrators ask most about DoDomain: providers, apex domains, SSL, SDKs, webhooks, monitoring, limits and testing, answered briefly.
Custom domains in multi-tenant Next.js
Resolve the tenant from the Host header in a Next.js 16 proxy.ts, mint and verify the customer's DNS records, terminate TLS on Vercel, and settle the apex.