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?

  • kamin@lemmy.kghorvath.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    You need to set up a local DNS server with a .servername zone and point your machines to it. You’d add an external DNS server like 1.1.1.1 as forwarder to allow internet traffic to still resolve.

      • novarime@sopuli.xyzOP
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        Yeah, how and where? In the docker compose? I have a dozem containers and is love if they were all a.server. b.server, c.server. How can I do this? Pihole DNS records don’t do anything at the port level.

        • jjakc@lemthony.com
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Sorry I meant in your browser. Yes dns does not point to ports.

          You would have to use some sort of reverse proxy that is only accessible from internal networks

    • novarime@sopuli.xyzOP
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      It’s the port that’s tripping me. How do I point jellyfin to that domain? It’s on docker on port 8096 - the hostname isn’t the problem, it’s the container.

      • plo@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Ah okay. You need some sort of reverse proxy.
        I really like caddy. Using it with caddy-docker-proxy in docker-compose makes it quite nifty:

        version: '3.7'
        services:
          whoami:
            image: containous/whoami
            networks:
              - caddy
            labels:
              caddy: http://whoami.mylab.home
              caddy.reverse_proxy: "{{upstreams 80}}"
        
        networks:
          caddy:
            external: true
        
        

        Just make sure to explicitly use ‘http’ instead of ‘https’. That way it won’t try to create certificates.

  • dan@upvote.au
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    You should be able to use mDNS pretty easily. Some services (like Home Assistant) support it out-of-the-box. mDNS is what powers the .local domains (eg homeassistant.local).

  • finn@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    I use pihole running on an esxi server for dns. In pihole you can create local dns records which is exactly what you’re trying to do. It’s very lightweight, you can run it on about anything.

    You can also do something like this

  • priapus@lemmy.one
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Reverse proxy and local DNS. Just add the domains you want to your DNS and point them at the reverse proxy.

  • asjmcguire@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    PiHole as your DNS resolver. LocalDNS mapping whatever hostname you want to whatever IP you want.
    Because I use Nginx Proxy Manager internally - then most of my hostname point to the Nginx IP address

  • Célia@pricefield.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    You can add an entry to your /etc/hosts file for the IP part, but this cannot remove the need to specify the port number as it is unrelated to the domain/IP

  • equidamoid@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    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.

    • zueski@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      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.

      • equidamoid@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        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 =)