this post was submitted on 02 Apr 2025
21 points (88.9% liked)

Selfhosted

61378 readers
195 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
 

Hello everyone.

I bought domain name (example.com) from https://njal.la/ and I want to direct it to my server but I need help with it.

Let's say that I have public and static home IPv4 address 10.172.172.172 (example) and on that address is a computer running on 192.168.200.101 (example) and there is jellyfin server (port 1020/tcp), immich server(port 1021/tcp) and bitwarden server (port 1022/tcp).

My question is can I create a subdomain and point it to these servers?

Like; jellyfin.example.com -> 192.168.200.101:1020

immich.example.com -> 192.168.200.101:1021

bitwarden.example.com -> 192.168.200.101:1022

Or do I have to buy two more separate domains for these servers? Like example2.com and example3.com?

Sorry for english and also if this is a stupid question but I need to know. I have never so far used domains and never dabbled in dns setting and I don't know where to search for info.

you are viewing a single comment's thread
view the rest of the comments

Don't mix your public and private DNS records. Use your public records for public things, and a local DNS forwarder for your local network.

A records only reference IPs and not ports.

SRV can be used to specify where to find ports, but the client needs to support those lookups to properly use it. You can use a reverse proxy or HTTP redirects to point things to different ports.