Attach a hostname
1
Add the hostname
Open the distribution’s Network page and add a fully qualified hostname such as
cdn.example.com.2
Save and copy the target
Save the network configuration and note the distribution’s root hostname.
3
Create DNS
Create a CNAME from the custom hostname to the distribution hostname. For an apex name, use the record type or flattening behavior supported by your authoritative DNS provider.
4
Wait for availability
The hostname can pass through draft or provisioning before it becomes active. Verify its certificate before redirecting all HTTP traffic.
Visitor TLS
enable_httpsserves the distribution over HTTPS.https_redirectredirects HTTP clients to HTTPS.enable_http3enables HTTP/3 where supported.- Protocol switches control SSL 3.0 and TLS 1.0–1.3 support.
Origin TLS
- Origin protocol controls whether edge nodes use HTTP, HTTPS, or the visitor’s protocol.
- Custom SNI hostname can match the Host header or use a fixed hostname.
- Origin TLS validation verifies the certificate presented by the origin.
Certificate selection
Use TLS Manager to inspect managed certificate issuance or import a certificate. In the distribution’s TLS configuration, select a certificate from the same project. HTTPS must be enabled before you attach one. The API accepts optionalcertificate_id. A positive ID selects a project certificate. An explicit 0 selects automatic management and can replace an imported certificate. Omitting the field preserves the existing binding when HTTPS is already enabled; it does not force an imported certificate back to managed mode.
Review certificate lifecycle for expiry, renewal, and troubleshooting.