/Docs
Search docs or ask a question⌘K
DocsAgent
Changelog
Guides Deployment Custom Domains

Custom Domains

Configure a custom domain for your Syntext documentation.

3 min read

Host your documentation at your own domain like docs.yourcompany.com instead of the default Syntext subdomain.

Prerequisites

•
Syntext Starter plan or higher (a wildcard hostname such as *.docs.example.com needs Pro)
•
Access to your domain's DNS settings
•
A deployed Syntext project

Setup Process

  1. 01Step 1 of 41 ›Step 11.
    Add Domain in Dashboard
    1.
    2.
    Select your project
    3.
    Navigate to Settings › Domains
    4.
    Enter your domain under Add a hostname: docs.yourcompany.com
    5.
    Click Add — the DNS records to create appear under the domain, each with a copy button
  2. 02Step 2 of 42 ›Step 22.
    Configure DNS

    Add a CNAME record pointing to Syntext, plus the TXT records listed under the domain — one proves you own it, the other lets the certificate be issued:

    TypeNameValue
    CNAMEdocscname.syntext.dev
    TXTas shown in the dashboardas shown in the dashboard
    Note

    DNS changes can take up to 48 hours to propagate, though most complete within 30 minutes.

  3. 03Step 3 of 43 ›Step 33.
    Verify Domain
    1.
    Return to Settings › Domains
    2.
    Click Check again next to the domain
    3.
    Wait for verification (usually 5-30 minutes)
  4. 04Step 4 of 44 ›Step 44.
    Deploy

    Your docs are served on the domain as soon as it's verified. Deploy once more so the sitemap, canonical links and social cards use the new domain:

    bash
    stx deploy

DNS Provider Guides

Cloudflare

1.
Go to your domain's DNS settings
2.
Add a CNAME record:
◦
Name: docs
◦
Target: cname.syntext.dev
◦
Proxy status: DNS only (gray cloud)
Warning

Disable Cloudflare's proxy (turn off the orange cloud) for the docs subdomain. Syntext handles SSL and CDN.

AWS Route 53

1.
Go to your hosted zone
2.
Click Create Record
3.
Configure:
◦
Record name: docs
◦
Record type: CNAME
◦
Value: cname.syntext.dev
◦
TTL: 300

GoDaddy

1.
Go to DNS Management
2.
Add a CNAME record:
◦
Host: docs
◦
Points to: cname.syntext.dev
◦
TTL: 1 Hour

Namecheap

1.
Go to Advanced DNS
2.
Add new record:
◦
Type: CNAME
◦
Host: docs
◦
Value: cname.syntext.dev
◦
TTL: Automatic

Google Domains

1.
Go to DNS settings
2.
Scroll to Custom records
3.
Add:
◦
Host name: docs
◦
Type: CNAME
◦
TTL: 3600
◦
Data: cname.syntext.dev

Root Domain

To use a root/apex domain (e.g., docs.com instead of docs.example.com), you need a DNS provider that supports ALIAS or ANAME records:

ProviderRecord Type
CloudflareCNAME Flattening (automatic)
AWS Route 53ALIAS
DNSimpleALIAS
NS1ALIAS
text
ALIAS @ → cname.syntext.dev
Note

Not all DNS providers support ALIAS records. If yours doesn't, use a subdomain like docs.yourcompany.com.

SSL Certificates

SSL certificates are automatically provisioned and renewed:

•
Issued by: Cloudflare, on Syntext's behalf
•
Type: DV (Domain Validated), validated through the TXT record above
•
Renewal: Automatic

No manual configuration needed.

CAA Records

If your domain has CAA records, they must allow the certificate authorities Cloudflare issues from — Let's Encrypt and Google Trust Services:

text
CAA 0 issue "letsencrypt.org"
CAA 0 issue "pki.goog"

Multiple Domains

Add multiple domains that all serve the same documentation:

•
docs.yourcompany.com (primary)
•
developers.yourcompany.com (alias)
•
help.yourcompany.com (alias)

All domains serve identical content.

Removing a Domain

1.
Go to Settings › Domains
2.
Click Remove next to the domain and confirm
3.
Remove the DNS record from your provider

After removal, the site returns to yourproject-docs.syntext.dev.

The domain is released and can be added to another project. Deleting a project, or its workspace, releases all of its custom domains the same way. To move a domain, add it to the new project and set up the DNS records the dashboard shows for it.

Troubleshooting

Domain Not Verifying

•
Confirm the CNAME and TXT records are correct
•
Wait up to 48 hours for DNS propagation
•
Check for conflicting A records
•
Verify no typos in the domain name

SSL Certificate Error

•
Ensure domain points to cname.syntext.dev
•
Check that CAA records (if any) allow letsencrypt.org and pki.goog
•
Remove any conflicting SSL configurations

Mixed Content Warnings

Ensure all assets use HTTPS or relative URLs:

markdown
<!-- Good -->
![Screenshot](/images/screenshot.png)
<!-- Avoid -->
![Screenshot](http://example.com/screenshot.png)

"Too Many Redirects"

If using Cloudflare:

1.
Set SSL mode to "Full" (not "Flexible")
2.
Disable "Always Use HTTPS" for the docs subdomain
3.
Turn off the orange cloud proxy
Was this page helpful? Yes No
Previous
Product
Resources
Company
© 2026 SyntextBuilt with Syntext