Root domains such as example.com are not supported as custom hostnames, including with CNAME flattening at your DNS provider. Use a subdomain such as cdn.example.com or www.example.com, and redirect the root domain to it.
CDN hostnames and SSL
Default hostname
Every CDN gets a hostname of the form prefix.b-cdn.net, where the prefix is chosen at creation. It is marked Main in the hostname list, has SSL enabled from the start, and cannot be removed.
Custom hostnames
You can add any number of custom hostnames, such as cdn.example.com, so that visitors see your own domain. Each custom hostname needs a CNAME record at your DNS provider pointing at the default b-cdn.net hostname. The hostname shows as CNAME missing until the record is found, and becomes Active once it is verified.
For the step-by-step flow, see How to get started with UpCloud CDN.
Root domains are not supported
DNS proxies
If your DNS provider proxies traffic, such as Cloudflare's proxy mode, disable it for the CDN record. A proxied record does not resolve to the CNAME target, so verification fails.
SSL certificates
Once a custom hostname is verified, you can enable SSL for it in one of two ways.
| Option | What it does |
|---|---|
| Free SSL | A Let's Encrypt certificate is issued for the hostname and renewed automatically. The hostname shows Provisioning for a short while, then Enabled. |
| Manual certificate | Upload or paste your own PEM-encoded certificate and private key. Renewal is your responsibility. |
Force SSL
Each hostname has a Force SSL toggle. When on, HTTP requests to that hostname are redirected to HTTPS. It is off by default, including on the main hostname. The same redirect can be applied to specific paths only with an edge rule.