Scalable compute services.
Simple object storage.
Run managed Kubernetes clusters.
Tools & Integrations
Automate your infrastructure.
Deploy pre-built applications.
Connect, share and learn
DevOps and development guides
Questions & Answers
Development and systems Q&A
by Justin Ellingwood
You have to point example.com to DigitalOcean Name Servers. Please let us point sub.example.com to DigitalOcean Name Servers.
Subdomain support for CDN SSL is an absolute requirement for me.Being locked into a particular DNS provider for 2nd level domains is a common situation, and in this case delegating to a 3rd level domain is also common. Restricting CDNs to a hostname followed by a 2nd level domain is arbitrary. It has no basis in any internet standard.
DigitalOcean's CDN service is useless to me in its current state.
We need this as well as a requirement to move forward in using DO Spaces CDN functionality
Ran into this issue last month. We manage our DNS externally and are locked into that for a while unfortunately. We tried to brand our CDN by adding a subdomain to DO but it wouldn't let us add it to a CDN. A way to point a subdomain to DO and use it for a CDN would be immensely helpful.
I'm in need of this as well. Technically, it should be completely possible to do since automated ACME DNS challenges can be done on subdomains as well.
As a solution in the interim, one could use the "Bring your own certificate" functionality and use the DigitalOcean API (https://developers.digitalocean.com/documentation/v2/#certificates) to automate the refreshing of certificates that way.
Hi Richard, I'm not sure what's not technically possible about pointing a subdomain to spaces. You can point a subdomain to any IP address.
To my knowledge, that's not technically possible as sub.example.com ISN'T a domain.
You won't be notified about changes to this idea.