Connect a domain managed at Cloudflare

This guide covers domains whose DNS is managed at Cloudflare. Before you start, add your custom domain in ComputeSphere and copy your service URL — for example d-silver-cobra-ab12c.computesphere.app.

Cloudflare supports CNAME flattening, so you can point both a subdomain and a root domain straight at your service URL with a CNAME.

Add the record

1. Sign in to the Cloudflare dashboard and select your domain.

2. In the left nav, go to DNS → Records.

3. Click Add record and enter:

   Field	Subdomain (www.example.com)	Root domain (example.com)
   Type	CNAME	CNAME
   Name	www	@
   Target	d-silver-cobra-ab12c.computesphere.app	d-silver-cobra-ab12c.computesphere.app
   Proxy status	DNS only (gray cloud)	DNS only (gray cloud)

4. Click Save.

Set the proxy status to "DNS only"

Click the orange cloud so it turns gray ("DNS only") before saving. If the record stays proxied (orange cloud), Cloudflare terminates TLS itself and ComputeSphere can't issue your certificate — the domain doesn't become Active.

Both root and www

To serve both example.com and www.example.com, add the same domains as custom domains in ComputeSphere and create a CNAME (DNS only) for each — @ and www — both targeting your service address. Cloudflare flattens the @ record automatically, so the apex needs no IP addresses.

Root domain via A / AAAA (alternative)

Cloudflare's CNAME flattening already serves a root domain, so most Cloudflare setups don't need this. If you prefer, you can instead point the apex straight at ComputeSphere's IP addresses with A and AAAA records. Use the exact addresses the Console shows when you add the domain, and set Proxy status to DNS only (gray cloud) on each:

Type	Name	Value
A	@	162.159.143.43
A	@	172.66.3.39
AAAA	@	2606:4700:7::31b
AAAA	@	2a06:98c1:58::31b

Add every address the Console lists. Use either the flattened CNAME or these A/AAAA records for the apex — not both.

After you save

Return to Console → Domains in ComputeSphere. The domain moves to Active once the record resolves and the SSL certificate is issued — usually within a few minutes. You don't upload or manage a certificate; ComputeSphere issues and renews it automatically.

Wildcard domains

For a wildcard (*.example.com), add the records ComputeSphere shows you. Every record that Cloudflare can proxy must be DNS only:

Type	Name	Target	Proxy status
CNAME	@ (the base name)	your service address	DNS only, not proxied
or TXT	_cf-custom-hostname	the value shown in the Console	Not proxied (a TXT record never is)
CNAME	*	your service address	DNS only, not proxied
CNAME	_acme-challenge	the value shown in the Console	DNS only, not proxied

Keep wildcard records DNS only

Proxied, the certificate can't be issued and subdomains won't be served. A wildcard has to be DNS only, like every other record that points at ComputeSphere.