DNS & Domains
SSL provisioning
DunOps doesn't manage TLS certificates directly — your CDN or hosting provider does. Here's how it works per platform.
How TLS works per platform
| Platform | How TLS is provisioned |
|---|---|
| Vercel | Auto-provisioned via Let's Encrypt when a custom domain is added and DNS resolves |
| Netlify | Auto-provisioned via Let's Encrypt on custom domain add |
| Cloudflare | Proxied traffic gets Cloudflare's shared or dedicated cert; origin cert optional |
| Fly.io | Auto-provisioned via Let's Encrypt when the app is reachable |
| Heroku | ACM (Automated Certificate Management) — free on paid dynos |
| Render | Auto-provisioned via Let's Encrypt on custom domain add |
| Railway | Auto-provisioned via Let's Encrypt |
Note
DunOps can add a custom domain to your deployment and verify its DNS is pointing correctly, but certificate issuance is handled by the platform. It usually takes under 5 minutes after DNS propagates.
Adding a custom domain from chat
chat
Add the custom domain app.example.com to my Vercel project
Connect example.com to my Netlify siteDunOps adds the domain to your provider and tells you which DNS record to set. Add that record through DunOps or your registrar's dashboard, and the platform will provision the certificate automatically once it resolves.
If the certificate isn't issuing
The most common cause is DNS not yet resolving to the provider. Check propagation first, then confirm the domain is added to the provider. Most platforms retry issuance automatically every few minutes.
Tip
Ask DunOps:
Is my Vercel custom domain verified for app.example.com? — it checks the domain status in real time.