Custom Hostnames

Paid plans can serve CDN assets from their own domain (for example cdn.example.com) instead of the default <cdnId>.assets.cdn.eulerstream.com subdomain. SSL certificates are issued and renewed automatically; the minimum supported TLS version is 1.2.

Each account can register exactly one custom hostname, and a hostname can only be registered to one account at a time. Wildcard hostnames are not supported.

Setup

1. Open the Image CDN dashboard and register your hostname under Custom Hostname.
2. Create the DNS records the dashboard shows you at your DNS provider:
   • a CNAME record pointing your hostname at assets.cdn.eulerstream.com, which routes the traffic itself;
   • an ownership verification TXT record, which proves you control the domain;
   • an SSL validation TXT record, which lets the certificate authority issue your certificate.
3. Use the Verify button on the dashboard to re-check progress. Verification usually completes within a few minutes of the records resolving; the dashboard lists any outstanding issues reported by the network while it is pending.

While verification is pending

Your default subdomain keeps working the entire time. The custom hostname starts serving traffic only once its status reaches Active; until then requests to it will fail at the DNS or TLS layer depending on which records have propagated.

Removing a hostname

Removing the custom hostname deletes its registration and reverts your CDN to the default subdomain. Removal works on any plan, so an account that downgrades is never stuck with a hostname it cannot detach. Re-registering a hostname afterwards requires a paid plan again.

Plan requirements

Registering or replacing a custom hostname requires a paid plan. Assets served through a custom hostname are subject to the same rate limits, CORS origins, and access settings as the default subdomain.