Selfhosted

61070 readers

1011 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Hairpin dns issue (lemmy.world)

submitted 3 months ago by mortalic@lemmy.world to c/selfhosted@lemmy.world

29 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

[–] FauxLiving@lemmy.world 4 points 3 months ago* (last edited 3 months ago) (1 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.

[–] mortalic@lemmy.world 1 points 3 months ago (1 children)

Ahh, so basically take dns off the aginet router.

[–] FauxLiving@lemmy.world 2 points 3 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.