20
submitted 1 year ago by [email protected] to c/[email protected]

How do you guys set internal domains?

Say i dont want to type 192.168.1.100:8096 and want a url instead, say jellyfin.servername - how would I go about that? I don't want it exposed online via reverse proxy. I don't need certs. No port forwarding on the router.

How do I type 'jellyfin.servername' into a browser and being up the jellyfin dashboard?

you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 0 points 1 year ago* (last edited 1 year ago)

After much suffering with local zones (mainly due to stubborn devices ignoring dns servers coming via dhcp and retarded corporate vpn messing with resolv.conf) I just use xxx.local.mydomain.tld with a small script that parses the leases files and updates the data via cloud flare api.

[-] [email protected] 1 points 1 year ago

Using a real domain also lets you get Let's Encrypt TLS certificates for the subdomains, by using DNS challenges.

I do the same thing - I use xxx.int.example.com and xxx.vpn.example.com for internal IPs and VPN IPs respectively.

[-] [email protected] 0 points 1 year ago

I ended up doing a similar thing for the same reasons, too many things ignoring my local dns. I ended up creating a subdomain for my house where all the A records had internal ips. I gave out fixed leases to the things with names though instead of dynamic dns updates.

[-] [email protected] 1 points 1 year ago

I have static ips for the server-ish things and few important devices too, but for the rest (swarm of shellys, esp32, etc.) I'm too lazy to maintain the list =)

this post was submitted on 17 Jun 2023
20 points (95.5% liked)

Selfhosted

39251 readers
247 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.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS