Except it isn’t. Saying is trivial is just gross generalization. It’s trivial to configure bind to have internal zones that aren’t resolvable publically. It all depends on configuration, such as reverse ns entries, zone accessibility, etc.
Comment on Self hosting with subdomains
BonkTheAnnoyed@lemmy.blahaj.zone 3 days agoIt trivial to get a list of all registered domains and subdomains and the IP addresses they map to. There are any number of paid services to make it easy (e.g. subdomainfinder.c99.nl) but I’m pretty sure there’s also a way to do it yourself.
wildbus8979@sh.itjust.works 3 days ago
BonkTheAnnoyed@lemmy.blahaj.zone 3 days ago
Actually, wait. Something you a said might actually be just what I’m looking for: you mean that I can have DNS entry for mydomain.com and no additional AAA records, and have a cert for nextcloud.mydomain.com (or wildcard maybe?) and somehow still be able to use name based virtual servers?
Hmmm. I thought I was going to be limited to path-based.
Explain more?
wildbus8979@sh.itjust.works 2 days ago
A solutrly. Simply use ACME with the DNS validation method. Using bind you’ll want to create keys and allow TXT access for those keys to the validation domains. That’s all you need the actual domain doesn’t need to be resolvable with an A/CNAME record. Internally you can run an entirely different DNS server to resolve your hosts, use hosts files, or use bind zones.
BonkTheAnnoyed@lemmy.blahaj.zone 3 days ago
Okay. Yup, that’s probably true. I’m not that deep into network stuff. But, if you’re just doing the basic, ‘ha.mydomain.com => 121.41.38.9’ that works out of the box with host based b-hosts, then yeah, you’ll get traffic on that within 24 hours.
I reckon if a person understands what you’re talking about though, they’re already doing better than most.
Bane_Killgrind@lemmy.dbzer0.com 2 days ago
This is kind of why I have wild card on my main domain… Nothing on www.