Question

Why does the Load Balancer require a TLD when using Let's Encrypt?

I have a top-level domain for a client registered at Go Daddy. Call it domain.com

I’d like to have a subdomain thereof be hosted at DO with a LB and SSL managed by the Let’s Encrypt support. Call it sub.domain.com

AFAICT, DO requires me to set the nameservers for domain.com to ns{1,2,3}.do.com and not the nameservers for just sub.domain.com.

I don’t want to have DO hijack all of the client’s DNS.

Is there a way to have sub.domain.com on a DO LB with SSL via Let’s Encrypt or am I stuck with TLD domain.com only?

Thanks!


Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

AFAICT, DO requires me to set the nameservers for domain.com to ns{1,2,3}.do.com and not the nameservers for just sub.domain.com.

Here I mean I have NS records for sub.domain.com not the TLD’s default nameservers.