Setting Up a Custom Domain
Use your own domain instead of docsbook.io for your documentation.
Required: Premium subscription ($29 one-time)
Why Use a Custom Domain?#
Benefits#
- 🎯 Branding — documentation under your own domain
- 📈 SEO — links to your domain improve your ranking
- 🔐 Trust — visitors see your domain, not someone else's
- 💼 Professionalism — looks like your own product
Examples#
❌ Without domain:
docsbook.io/mycompany/product
✅ With domain:
docs.mycompany.com
Requirements#
-
Your own domain — registered by you
-
Premium subscription — $29 one-time
- If you haven't upgraded yet — do it now
-
Access to DNS settings — at your domain registrar
Step 1: Open Settings#
- View your documentation while logged in
- Click the Float Widget in the bottom right
- Open Settings
Step 2: Enter Your Domain#
In the Custom Domain section:
- Enter your domain (e.g.,
docs.example.com) - Click Save
Docsbook will generate the DNS configuration.
Step 3: Update DNS#
Docsbook will provide instructions:
Add a CNAME record:
Type: CNAME
Name: docs (or @)
Value: cname.vercel-dns.com
Where to Change DNS?#
Open the control panel of your domain registrar:
GoDaddy#
- Open godaddy.com → Sign in
- My Domains → Select domain → DNS
- Click "Add" next to DNS
- Fill in:
- Type: CNAME
- Name:
docs - Points to:
cname.vercel-dns.com
- Save
Namecheap#
- Open namecheap.com → Sign in
- Domain List → Manage
- Advanced DNS
- Add new record:
- Type: CNAME
- Host:
docs - Value:
cname.vercel-dns.com - TTL: 3600
- Save
Google Domains#
- Open domains.google.com
- Select domain
- DNS → Custom records
- Create new record:
- DNS Record Type: CNAME
- Name:
docs - Data:
cname.vercel-dns.com
- Save
1and1 / Ionos#
- Sign in → Domains
- Select domain
- Manage DNS
- Add record:
- Type: CNAME
- Subdomain:
docs - Alias:
cname.vercel-dns.com
- Save
Using a Root Domain#
If you want example.com (without docs):
-
Our recommendation: use
docs.example.com- Easier to configure
- Lets you use
example.comfor the project site
-
If you still want root:
- Some registrars don't allow CNAME on root
- Use an A record instead of CNAME:
76.76.19.0 - Contact support@docsbook.io for help
Step 4: Wait#
After adding the DNS record, updates propagate:
- Usually: 15-30 minutes
- Maximum: 48 hours
- Check status: use DNSChecker
Enter your domain → it should show cname.vercel-dns.com
Step 5: SSL Certificate#
Once DNS propagates, Docsbook automatically:
- Detects your domain
- Creates an SSL certificate (Let's Encrypt)
- Enables HTTPS
Your site is available at:
https://docs.example.com ✅
Verifying Your Domain#
How to check everything is working?#
Method 1: Simple check
- Open in browser:
https://your-domain.com - Your documentation should load
Method 2: DNS check
# In terminal
nslookup docs.example.com
# Should show: cname.vercel-dns.comMethod 3: Online service
- Open mxtoolbox.com
- CNAME lookup
- Enter your domain
- Should show
cname.vercel-dns.com
Troubleshooting#
DNS Not Updating#
Problem: 2+ hours have passed, but domain doesn't work
Solutions:
- Clear browser cache (Ctrl+Shift+Delete)
- Use a private browser window
- Check DNS via DNSChecker
- Verify the CNAME record is added correctly
- Wait another 24 hours
Old Site Still Showing#
Problem: DNS updated, but old version of site
Solutions:
- Press Ctrl+F5 (full cache clear)
- Open in private window
- Wait 24 hours
HTTPS Not Working#
Problem: https:// shows a certificate error
Solutions:
- Wait 1 hour — certificate is being created
- Make sure DNS has updated
- Check domain name for typos
- Contact support@docsbook.io
Domain Shows Vercel or Error#
Problem: Visiting the domain shows a Vercel message
Solutions:
- Check the domain is added in Docsbook (visible in Settings)
- Make sure the DNS CNAME is correct
- Wait 1-2 hours for sync
Changing Your Domain#
How to switch to a different one?#
- Open settings
- Change the domain in the Custom Domain field
- Click Save
- Update DNS for the new domain
- The old domain will stop working
Removing Your Domain#
How to go back to docsbook.io?#
- Open settings
- Clear the Custom Domain field
- Click Save
Documentation returns to:
docsbook.io/username/repo
Best Practices#
1. Use a Subdomain#
✅ docs.example.com
✅ guide.example.com
✅ api.example.com
❌ example.com (if your main site is there)
2. Tell People About the Domain#
Update links to your documentation everywhere:
- GitHub README
- Project website
- Email signatures
- Social media
3. Set Up Email (Optional)#
Now that you have a domain, you can add email:
- Google Workspace — professional Gmail
- Zoho Mail — free option
- Protonmail — private email
This is a separate service from Docsbook, configured through your registrar.
4. Use for SEO#
Now that the site is under your domain:
- Set up Google Analytics
- Track traffic
- Submit to search engines