this post was submitted on 04 Jan 2026
128 points (97.8% liked)

Selfhosted

61929 readers
409 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I created a short tutorial on using sub domains to access services hosted within my home network, thought I would share it here in case anyone finds it useful

This is the first time I've made a technical tutorial so apologise if there are mistakes/its confusing, feedback will be appreciated

you are viewing a single comment's thread
view the rest of the comments
[–] wildbus8979@sh.itjust.works 5 points 8 months ago* (last edited 8 months ago) (2 children)

Except it isn't. Saying it 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.

You can have (sub)domains that are listed in the certificate lists and yet aren't resolvable externally as well.

[–] BonkTheAnnoyed@lemmy.blahaj.zone 1 points 8 months ago* (last edited 8 months ago) (1 children)

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 CNAMEs, 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 points 8 months ago* (last edited 8 months ago)

Absolutely. 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. Fear not, this isn't exclusive to bind, ACME tools supports dozens of other backends. 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 0 points 8 months ago* (last edited 8 months 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 name based virtual hosts and reverse proxy, 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.