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

October 11, 2018 535 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!

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.

Have another answer? Share your knowledge.