Key idea
Adding a domain in ComputeSphere doesn't send anyone to it. You create the record from the DNS configuration table at your DNS provider, and ComputeSphere takes it from there.
From your domain to HTTPS
You do
In ComputeSphere, on the service's Custom Domain card: app.example.com
At your DNS provider, exactly as the table lists it:
CNAMEappd-hello-web-3f9c2a71.computesphere.app
ComputeSphere does
Fix the record, check it with dig @1.1.1.1, then choose Verify now.
Only the records in the table
The table in the Add custom domain dialog lists each record as Type, Name and Value. For an ordinary domain that's one record per name, pointing at your service's default hostname. There's no separate verification record: ComputeSphere proves you own the domain once it points at the service.
Copy the values rather than typing them. One wrong character is the most common reason a domain never goes live.
Subdomains: one CNAME
For app.example.com, www.example.com or any other subdomain, create a CNAME:
| Type | Name | Value |
|---|---|---|
| CNAME | app | d-hello-web-3f9c2a71.computesphere.app |
Most providers want only the part before your domain in Name (app, not app.example.com). Some show the full name after saving; that's fine.
Adding example.com also sets up www.example.com, so give www its own CNAME to the same hostname.
If you use the bare domain (example.com)
DNS doesn't allow a CNAME on the apex, so providers handle it differently. The console detects your provider and shows the right record:
- Cloudflare: a CNAME with name
@, which Cloudflare flattens for you. - Providers with ALIAS or ANAME records (DNSimple, DNS Made Easy, NS1): an ALIAS with name
@. - Everyone else (Namecheap, GoDaddy, Route 53 and others): A and AAAA records with name
@, pointing at the addresses shown.
If your provider can't point the apex at all, make www.example.com your main address and redirect example.com to it at your provider. The console suggests this under Can’t add this record?
Cloudflare: turn the proxy off
Cloudflare can proxy traffic through its own network (the orange cloud). That blocks validation and the certificate, and the domain gets stuck. Set Proxy status to DNS only, the grey cloud, on every record you add. The console marks these records DNS only (grey cloud).
Then wait
DNS changes usually show up within minutes. ComputeSphere keeps checking on its own, every few minutes at first and then every 15 minutes, so there's nothing else to do.
Not found for a minute? Check from outside
If your computer looked the name up before the record existed, it may remember “not found” for a few minutes. The same happens with a brand-new default URL. It only affects your view.
Ask a public DNS server instead:
dig @1.1.1.1 app.example.com CNAME +short
If it prints your service's hostname, the record is right and your cache will catch up. On Windows, nslookup app.example.com 1.1.1.1 does the same.
Check yourself