Comment on How to reverse proxy?

• HelloRoot@lemy.lol ⁨1⁩ ⁨month⁩ ago

  1. you rent a domain

  2. in the config (provided by the service where you rented the domain) you set it to point to the IP of the device where you run caddy

  3. the service tells the relevant global DNS servers your setting

  4. your DNS does a DNS lookup and a DNS server returns the IP you configured it to point to

  ---

  Depending on the DNS you use, you can manually add entries to do 1-3 differently, but that will only work for devices that use your DNS

  source

  • beeng@discuss.tchncs.de ⁨1⁩ ⁨month⁩ ago

    Is this a local address or a public IP address?

    I just want the resolving internal to my network but I never got it working right.

    source

    • Scrath@lemmy.dbzer0.com ⁨5⁩ ⁨weeks⁩ ago

      I’m not the guy you replied to but personally I use a setup called split-horizon DNS.

      1. I have a DNS server running on a raspberry pi which I have set up as the DNS server for all devices in my local network (by setting it in the router).
      2. This DNS server has my domain name as an A record pointing to my reverse-proxy (Nginx Proxy Manager), e.g. example.com would resolve to 192.168.0.100.
      3. Any subdomain I want to use is set up as a CNAME record in my DNS server referring to the previously configured A record with my domain. (jellyfin.example.com => example.com)
      4. Now all requests to the registered domain and subdomain are routed to my reverse-proxy which I configured to forward them to the correct service depending on the given subdomain.

      This is a little bit of a simplification. I also use a cloudflare tunnel to allow access to select subdomains and I have 2 reverse-proxies chained together since NPM can resolve services by their container name as long as they are in the same docker network.

      Also probably important: My DNS server was a pi-hole (until today at least) and did not act as my DHCP server. This meant it had no idea of local device hostnames and therefore was configured to forward queries to local device names to my routers built-in DNS server.

      source

      • DevotedOtter@lemm.ee ⁨5⁩ ⁨weeks⁩ ago

        I’m looking to do something like this. I’m uneasy about having the registered domain pointing towards my IP address (partially because I’m unsure of the exact risks and partially because I’d rather do it internally if possible).

        You said you were using pihole. What did you change to and why did you change? Pihole seems the most recommended from what I’ve seen?

        source

        • -> View More Comments
    • PlexSheep@infosec.pub ⁨5⁩ ⁨weeks⁩ ago

      If you want DNS only in your LAN, you need to self host a DNS server and register this domain locally (by putting it in some config file of yours)

      source
• WhyJiffie@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago

  if you don’t want to rent a domain, but you run a local DNS server (pihole, technitium) for filtering or other reasons, you can register your own domain names in there, for free. but don’t use common TLDs to avoid conflicts, and leave “.local” alone too because that’s used by mdns/avahi. You may use .home, .lan, or a few others I don’t know without looking them up

  source