Question

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

Posted October 11, 2018 787 views
Load Balancing

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!

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.

×
1 answer
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.

  • Just tried it and that’s a bummer! Hopefully support for FQDNs regardless of their label level is on the roadmap as I need that functionality for my clients.

Submit an Answer