Custom domains
These commands attach your own domain to the saved deploy target and check its status.
On this pageAdd or remove a custom domain · List domains · Check DNS and certificate status
void domain add
void domain add <hostname> [--project <name>]Adds a custom domain to the saved target.
- Hosted SDK projects print the DNS records needed for SaaS hostname validation.
- Direct Cloudflare projects add a
custom_domainroute and sync only the route config right away. Cron, queue and workflow triggers do not change. Cloudflare manages the DNS record and TLS certificate in a zone on the pinned account.
If you still use the old singular route field, convert it to a routes array first. Otherwise the new domain could hide the existing route.
Wildcard hostnames (
*.example.com) are not supported. Register each subdomain on its own.
void domain delete
void domain delete <hostname> [--project <name>]Direct Cloudflare projects apply the change right away. Deleting the last custom domain needs your void cloudflare login session or an API token with Workers Scripts: Edit. If Cloudflare rejects the change, the SDK tries to restore the previous domain config. It reports whether that worked.
void domain list
void domain list [--project <name>]Lists all custom domains. Hosted projects show the active or pending state from the platform. Direct Cloudflare projects list the custom-domain routes in void.config.ts.
void domain status
void domain status <hostname> [--project <name>] [--verbose]Shows domain verification and TLS certificate status. It lists the DNS records to set and any action you must take. A domain goes live once verification and certificate issuance finish.
For direct Cloudflare projects, status only reports whether the route is in the Void Cloudflare config. It does not check remote certificate issuance. Cloudflare owns that state and shows it in the dashboard. --project only works for hosted projects.
