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?

      • novarime@sopuli.xyzOP
        2·
        2 years 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
          6·
          2 years 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

        • Captain Janeway@lemmy.world
          1·
          2 years ago

          Just to clarify a bit further. You browser doesn’t specify ports in the URL because HTTP and HTTPS have basically coopted the 80/443 ports. You could have a website running an HTTP server on another port like 3000. But then you’d need to specify the port in the URL since the browser - by default - is looking at 80/443 and not 3000.

          You should be able to configure the port for your Jellyfin server. I’m not a Jellyfin user, but most applications allow you to pick a port to run it on. So you’ll have to change the port to port 80 and then expose that port on your docker container in the docker-compose file.

          Edit: actually now that I think about it… You could just point your local port 80 to the docker container port. I forget the port mapping schema but it’s something like

          ports:
  - 80:1234

          You might have to flip the order of the ports. But basically that example above is trying to map port 80 to port 1234. If that fails, you might have port 80 being used by another application on your computer and you’d either have to shut that app down, pick a different port for that app or you’re back to picking a different port for Jellyfin

    • novarime@sopuli.xyzOP
      1·
      2 years 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
        6·
        2 years 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.

  • ilovetamako@lemmy.fmhy.mlEnglish
    8·
    2 years ago

    I use a pi hole instance for this. I just point all the subdomains at my ngnix server and reverse proxy everything through that

  • finn@lemmy.worldEnglish
    6·
    2 years 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

  • TheButtonJustSpins@infosec.pubEnglish
    5·
    2 years ago

    You don’t need to expose it to the web to use a reverse proxy. You can use traefik, caddy, nginx, or any other reverse proxy to serve IP:PORT on domain.tld. You can use 80 or 443 as you’d like.

    If you’re using docker, it’s even easier. How are you hosting your jellyfin?

  • asjmcguire@kbin.social
    4·
    2 years 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

  • philipcristiano@lemmy.philipcristiano.comEnglish
    2·
    2 years ago

    Running a reverse proxy then adding your IP to your router/other-DNS-server will make it easy ish. Just don’t pick a domain that is used by other people. If you have a(ny) domain you own then a subdomain you set in your router is fine/safe.

    I have *.[house domain] point to a static IP set in my router. The IP is announced via BGP to point to running Traefik instances as a reverse proxy that points to the appropriate container. This also gives certs, but isn’t required.

  • kamin@lemmy.kghorvath.comEnglish
    2·
    2 years 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.

  • priapus@lemmy.oneEnglish
    2·
    2 years ago

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

  • dan@upvote.auEnglish
    2·
    2 years 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).