13
Hairpin dns issue (lemmy.world)
submitted 7 months ago by to c/selfhosted@lemmy.world
28 comments fedilink hide all child comments
 

I've got Immich working great on Unraid, but if I'm on my network I can't really use it. Just fails to resolve the dns. I looked it up and it's that my router doesn't support hairpin or something. It's a Aginet hb810. I found a workaround in the Immich client where you can add a second entry that's network specific, but it doesn't seem to work very reliably.

What are my options?

you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 7 months ago* (last edited 7 months ago) (2 children)

On your LAN DNS server (say, pi-hole), you could add an A record for your Immich's domain name that points to the internal IP address so clients on your LAN would simply resolve the LAN IP instead of trying to do fancy NATing. Make sure your browser doesn't try to do DNS over HTTPS, which would skip your local dns.

Or you could run everything on a meshVPN like Tailnet. That way the (VPN) IP of the Immich server doesn't change and the Tailnet will route the traffic over your LAN when your clients are local.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 7 months ago (1 child)

    Ahh, so basically take dns off the aginet router.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 7 months ago

    Yeah, setup a pi-hole container/server to do DHCP and disable it on your router. The documentation should cover it, but you have to use network_mode: host in order for it to do DHCP.

    You can then add an A record entry for your Immich server's domain name pointing to the LAN IP and so any device on your LAN will resolve its domain to the LAN IP.

    You also get pi-hole DNS filtering/adblock and, probably, a larger DNS cache than what the router provides.

  • permalink
  • fedilink
  • source
  • parent