D

Custom Domains

Bind a domain you own to a Dokki publish site. Pro only.

Why use a custom domain

  • Brand — docs.your-company.com instead of a dokki.one/pub/... URL.

  • SEO — your published content earns authority for your domain.

  • Trust — visitors know they're on your site, not a shared host.

  • No "Powered by Dokki" footer — removed automatically on Pro custom-domain sites.

Setting it up

1. Add the domain in Dokki

Open Settings → Publishing → Custom Domain → Add domain. Enter the full hostname (for example docs.your-company.com). Dokki shows you a DNS record to add.

2. Add the DNS record

In your DNS provider (Cloudflare, Route 53, Google Domains, etc.), create the CNAME record exactly as Dokki shows you — copy the Value field straight from the screen, since it's specific to your domain.

For apex domains (example.com with no subdomain), you'll need a provider that supports ALIAS or ANAME records, or use a www. subdomain instead. Cloudflare's CNAME flattening makes apex domains "just work" if you use Cloudflare for DNS.

3. Wait for verification

Dokki checks your DNS automatically. Once the record resolves correctly:

  • The domain status flips to Verified.

  • An SSL certificate is provisioned automatically (usually within a minute).

  • Visitors can hit https://docs.your-company.com/... and see your site.

If it isn't working

  • Wait a few minutes. DNS changes don't propagate instantly — give it 5 to 10 minutes.

  • Check the CNAME value. Make sure it matches exactly what Dokki shows you.

  • Turn off the proxy. If you use Cloudflare, the orange-cloud proxy can interfere with verification. Set it to "DNS only" (gray cloud) until verified.

Removing a domain

Open Settings → Publishing → Custom Domain → Remove. The domain unbinds on Dokki's side; remove the CNAME from your DNS provider too. Old dokki.one/pub/... URLs continue to work whether or not you have a custom domain bound.

Wildcards and multiple domains

  • A workspace site can have one custom domain at a time.

  • Multiple Pro workspaces can each bind their own domain.

  • Wildcard domains (*.your-company.com) are not supported — bind specific subdomains.