Custom Domains
Serve your docs from your own domain instead of the default *.jamdesk.app subdomain. DNS setup for subdomains and apex domains, SSL, and verification.
Serve your docs from your own domain instead of the default *.jamdesk.app subdomain.
For a step-by-step dashboard walkthrough and DNS troubleshooting, see the Help Center guide.
Setup Overview
Go to your project Settings → Domain and enter your domain (e.g., docs.example.com or example.com).
Add the DNS records shown in the dashboard to your DNS provider. The records depend on your domain type (see below).
Jamdesk verifies ownership and provisions an SSL certificate automatically.
DNS Configuration
The records you need depend on whether you're using a subdomain or an apex (root) domain.
Subdomains (e.g., docs.example.com)
| Type | Name | Value |
|---|---|---|
| CNAME | docs | cname.vercel-dns.com |
| TXT | _jamdesk.docs | (shown in dashboard) |
The "Name" field is just the subdomain portion. For docs.example.com, enter docs.
Apex Domains (e.g., example.com)
| Type | Name | Value |
|---|---|---|
| A | @ | 76.76.21.21 |
| TXT | _jamdesk | (shown in dashboard) |
Apex domains use an A record instead of CNAME because DNS standards (RFC 1034) prohibit CNAME records at the zone apex.
DNS changes can take up to 48 hours to propagate, though most complete within minutes. Check status at whatsmydns.net.
Verification
After adding DNS records, Jamdesk automatically:
- Detects your DNS records (CNAME or A record, plus TXT)
- Verifies domain ownership via the TXT record
- Provisions an SSL certificate via Let's Encrypt
- Routes traffic to your documentation
Check verification status in Settings → Domain. Status shows as:
- Pending - Waiting for DNS propagation
- Active - Domain verified and serving traffic
- Error - Configuration issue (see details in dashboard)
SSL Certificates
SSL certificates are provisioned automatically and renewed before expiration. HTTPS is required—HTTP requests redirect to HTTPS.
No manual certificate configuration needed.
Root Domains
Root (apex) domains like example.com are fully supported. The dashboard automatically shows the correct records — an A record pointing to 76.76.21.21 instead of a CNAME, since DNS standards prohibit CNAME records at the zone apex.
If you prefer a subdomain like docs.example.com, that works too.
Multiple Domains
Each project supports one custom domain. For multiple domains pointing to the same docs:
- Set up your primary domain in Jamdesk
- Configure additional domains to redirect to the primary at the DNS/CDN level
Removing a Domain
To disconnect a custom domain:
- Go to Settings → Domain
- Click Remove Domain
- Your docs remain accessible at the
*.jamdesk.appsubdomain
Cloudflare Users
If using Cloudflare as your DNS provider:
- Set proxy status to DNS only (gray cloud icon) during domain verification
- Let Vercel handle SSL—disable Cloudflare's "Always Use HTTPS" for the docs subdomain
- After verification completes, you can re-enable proxying (orange cloud)
Using a Cloudflare Worker? The DNS record must be proxied (orange cloud) for the Worker to run. Use gray cloud only during verification, then switch back. See Cloudflare Workers setup for details.
Troubleshooting
| Issue | Solution |
|---|---|
| Domain stuck on "Pending" | Check DNS records with dig (CNAME for subdomains, A for apex) |
| SSL certificate errors | Ensure no CAA records block Let's Encrypt |
| Redirect loops | If using Cloudflare, set to gray cloud during verification (see Cloudflare Users above) |
| CNAME not resolving | Verify record at DNS provider, wait for propagation |
For detailed diagnostics, see DNS Troubleshooting.