Hi,
I’ve noticed that Let’s Encrypt-certificates managed by Digital Ocean (created in the Security-tab of the Control Panel) will always be issued with the root domain name as CN, even thou I want then issues only for certain subdomains (these seem to be added as SAN’s). This is a problem because at some point (I assume when I set the certificate to be used in a kubernetes loadbalancer service) DNS records are created for all domains covered by the certificate, including the root which is already pointing at another location.
Is there a way to make it use only the subdomain, or at least prevent it from creating DNS entries if one already exists for the same name?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Sir,this cant be modified.But if you want to just use you subdomain as CN and SAN,please generate a wildcard SSL by youself and upload it to panel.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.