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

Selfhosted

54297 readers
284 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 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
[–] mike_wooskey@lemmy.thewooskeys.com 3 points 3 days ago (1 children)

Not positive, but I think you left in a reference to real info (twilightparadox.com) instead of "example-fying" it (mydomain.com), in the paragraph just before section 4:

For example say I have home-assistant running on a Pi with the local address 192.168.0.11, I could create a subdomain named ha that has the value mysub.twilightparadox.com then create the following nginx config

server{
	listen 80;
	server_name ha.mydomain.com;
	resolver 192.168.0.1;
	location / {
		proxy_pass http://192.168.0.11/;
	}
}

When nginx sees a request for ha.mydomain.com it passes it to the address 192.168.0.11 port 80.

[–] JackDavies@lemmy.world 1 points 3 days ago (1 children)

I'm not sure which reference you are referring to, twilightparadox.com is a domain on the dynamic DNS service, mysub is also an example

[–] atzanteol@sh.itjust.works 0 points 3 days ago (1 children)

Section 1 says you're using freedns.afraid.org though.

[–] JackDavies@lemmy.world 1 points 3 days ago

freedns.afraid.org is the site you use to manage the dynamic DNS twilightparadox is the default free option for creation DNS records on that comes so I used that as an example