Custom domain DNS
The CNAME record, what it points at, what to do while you wait.
The mechanics behind the Custom domain feature, in case the abstracted version doesn't tell you enough.
What you create
One DNS record on the domain you want to use (e.g. on acme.com if your goal is support.acme.com):
| Type | Name | Value | TTL |
|---|---|---|---|
| CNAME | support | acme.nura24.com |
3600 |
That's it. Just the CNAME. No A records, no AAAA, no separate certificate.
Where to create it
At whatever service manages your DNS:
- Cloudflare — DNS tab, Add record, CNAME, name
support, targetacme.nura24.com, Proxy off (orange cloud OFF — leave DNS-only). Save. - Google Domains / Squarespace Domains — DNS section, add custom record.
- GoDaddy / Namecheap / etc. — same flow under "DNS records".
- Route 53 — Hosted zone for your domain → create record → CNAME.
Cloudflare proxy gotcha
If you use Cloudflare and accidentally leave the proxy ON (orange cloud), the CNAME resolves through Cloudflare's edge before reaching us, and our automatic SSL provisioning fails. Turn the proxy off (gray cloud / DNS only). You don't lose Cloudflare's caching for your main site — only the support. subdomain.
Propagation
DNS changes take seconds to hours depending on your TTL. Our verifier polls every few minutes. If you set TTL=300 (5 min), the record reaches us within 5 minutes after you save.
You can check propagation yourself before our verifier picks it up:
dig +short CNAME support.acme.com
# should output: acme.nura24.com.
If dig returns nothing or returns the wrong target, the record hasn't propagated yet. Wait.
After verification
Once the CNAME resolves correctly, we automatically:
- Issue a Let's Encrypt SSL certificate.
- Renew it every 60 days, well before expiration.
- Serve your custom domain alongside the original subdomain.
Both URLs stay alive — support.acme.com AND acme.nura24.com. We don't auto-redirect one to the other (you can if you want, on your end).
Removing the custom domain
In Nura24: Settings → Custom domain → Remove. We revoke the SSL cert.
On your DNS side, you can delete the CNAME at your leisure — leaving it in place after removing the Nura24 setup just means the subdomain resolves to a 404.