Connect your domain

Add your domain#

Open the Domains tab inside your project and add your hostname. CloudAuro shows the exact DNS records to create at your domain provider.

Update your DNS records#

Add the TXT ownership record and the CNAME routing record as shown. Apex domains may need DNS flattening or an A record to the CloudAuro public server IP. Keep the TXT record in DNS for periodic ownership checks.

Verify the connection#

Select verification after changing DNS. Changes can take time to propagate. Hosting and certificate authorization remain pending until ownership and routing checks pass. HTTPS requires a configured public CloudAuro server and Caddy. You can remove the domain from this tab.

Cloudflare-protected custom domains#

When CloudAuro uses Cloudflare for SaaS, add the TXT ownership record and a DNS-only CNAME pointing to customers.cloudauro.com. Select Check DNS. After ownership is confirmed, CloudAuro requests the hostname and HTTPS certificate from Cloudflare. Refresh to see any additional TXT records required for hostname and certificate verification. Keep all required verification records in place.

A domain becomes Connected only after ownership, the CNAME target, and both Cloudflare hostname and HTTPS statuses are verified. Pending checks retry approximately every five minutes. Start with www or another subdomain; root domains, flattened CNAME records, and proxied customer-side DNS records are not supported by this initial verifier. Do not point an A record at CloudAuro's origin server.

Removing a domain also removes its Cloudflare custom hostname. If the provider is unavailable, the removal remains pending for you to retry. Your generated CloudAuro address continues to work. Operators must configure the Cloudflare account, API credentials, origin HTTPS, and server first; adding DNS does not make a localhost server public.