Docsalot home pagelight logo
  1. Customization
  2. Cloudflare Custom Domains

If your domain uses Cloudflare DNS, the custom-domain workflow has one extra important requirement: the CNAME record must be DNS only while Docsalot verifies and provisions the domain.

Cloudflare’s orange-cloud proxy can interfere with custom hostname verification and SSL provisioning. Use the grey-cloud DNS-only setting unless Docsalot support explicitly tells you otherwise.

​
Agent-First Flow

If you use Claude Code, Codex, or another coding agent with the Docsalot CLI skill installed, start with this prompt:

use docsalot cli to point this documentation to docs.yourdomain.com. My DNS is on Cloudflare, so make sure the CNAME is DNS only and tell me exactly what record to add.

Your agent should:

  1. Find or ask for the Docsalot documentation ID.
  2. Run the custom-domain setup through the Docsalot CLI.
  3. Show you the CNAME record Docsalot returns.
  4. Remind you to set the Cloudflare record to DNS only.
  5. Re-run verification once DNS is ready.

​
Manual CLI Flow

Add the domain:

docsalot domains add --documentation-id <documentation-id> --domain docs.yourdomain.com

The CLI returns a CNAME record. In Cloudflare, create that CNAME record with:

Proxy status: DNS only

Then verify the domain:

docsalot domains verify --documentation-id <documentation-id> --hostname-id <hostname-id>

​
Cloudflare Checklist

  • Use a customer-owned hostname such as docs.yourdomain.com.
  • Create the CNAME record returned by Docsalot.
  • Set the CNAME to DNS only / grey cloud.
  • Wait a few minutes for DNS propagation.
  • Run docsalot domains verify after the record is visible.

​
Common Cloudflare Issues

​
Related Pages