Configure a CNAME
To serve a custom domain through the Paradarum CDN you create a single DNS record at your DNS provider: a CNAME that points your hostname at your property's system hostname. Once that record resolves to a Paradarum point of presence (PoP), the hostname activates and a certificate is issued.
The CNAME target
Every property is automatically assigned a system hostname under a Paradarum-controlled domain, in the form your-property.prdrm.net (for example my-site.prdrm.net). This system hostname is the target of your CNAME — all custom hostnames you add to the property point at it.
You can copy the exact target from your dashboard: open the property, go to the Hostnames tab, and use the copy-to-clipboard button in the DNS Configuration Required dialog's CNAME card.
If the panel shows System hostname not found. Please contact support., the property has no system hostname assigned and you should open a ticket before configuring DNS.
The DNS record to create
At your DNS provider, create a record like the following. Replace www.example.com with your hostname and my-site.prdrm.net with your property's system hostname.
Type: CNAME
Name: www.example.com
Points to: my-site.prdrm.net
In zone-file form:
www.example.com. CNAME my-site.prdrm.net.
After saving the record, allow 5-10 minutes for DNS propagation, then return to your dashboard to verify DNS and issue the certificate.
How verification works
Paradarum does not use a TXT or CNAME ownership token. Verification is a plain forward DNS lookup: the API resolves your hostname and checks whether it resolves to any active PoP IP (a PoP that is healthy and has traffic enabled). Because resolvers follow CNAMEs automatically, a CNAME to your-property.prdrm.net is enough — the lookup ends up at a PoP address.
DNS is considered valid the moment your hostname resolves to any active PoP IP. There is no per-record token to copy or paste.
The apex/root domain caveat
The DNS specification does not allow a CNAME record at the apex (root) of a zone — for example example.com itself, as opposed to www.example.com. You have two options:
- Use a subdomain. Point a subdomain such as
www.example.comorcdn.example.comat your system hostname with a CNAME, then redirect the apex to it. - Use a provider ALIAS/ANAME. Many DNS providers offer a flattening record type (often called
ALIAS,ANAME, or "CNAME flattening") that behaves like a CNAME but is legal at the apex. Point it atyour-property.prdrm.net.
Do not try to add a literal CNAME at the apex — most providers will reject it, and those that accept it can break other records (MX, TXT, NS) for the zone. Prefer a subdomain or an ALIAS/ANAME.
Advanced: A record to a PoP IP
As an alternative to a CNAME you can point an A record directly at a Paradarum PoP IP. This is an advanced setup and the IPs can change, so contact support for the current PoP addresses before using it. A CNAME to your system hostname is the recommended approach because it tracks PoP changes automatically.
Next steps
- Add the custom hostname to your property first if you have not already.
- Verify DNS and retry SSL once the CNAME is live.
- Learn how SSL/TLS certificates are issued and managed.