Managed Let's Encrypt certificate is always uses "root" domain name as CN, even thou I've selected subdomain(s)
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?
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.×