• 0 Posts
  • 4 Comments
Joined 3 years ago
Cake day: June 23rd, 2023
  • spaghetti_carbanana@krabb.orgtoSelfhosted@lemmy.world•Hairpin dns issueEnglish
    1·
    3 months ago

    You’ve got two options I can think of:

    1. As others have eluded, split DNS. You need something handling DNS resolution internally that allows you to add custom records. You’ll need to add a record of type “A” pointing to the internal IP where Immich sits.

    2. Since you have Immich published to your public IP, you can use hairpin NAT. This is something that is a lucky dip with routers as to whether it works or not and only some make it configurable. This will allow you to hit Immich via public IP and the router will “hairpin” the traffic out to the WAN interface and back in. This is how I do it so I don’t make a spaghetti mess of DNS records.

    Failing to resolve DNS doesn’t sound like this is actually the problem though. Do you have a domain registered and DNS records pointing to your public IP? Does it resolve fine outside your network? If yes, then something may be wrong on your internal network’s DNS resolution.

    Also worth noting, if you only just created the records in public DNS then tried to resolve it straight away, they will not have propagated yet and your DNS resolver will cache the “record doesn’t exist” result for some time (most I’ve seen is a couple of hours).

  • spaghetti_carbanana@krabb.orgtoSelfhosted@lemmy.world•What access points do you use?English
    4·
    2 years ago

    Its not for everyone but I use Cisco Aironet APs with a virtual wireless LAN controller. Ubiquiti is popular among the community. They’re cost effective and work well in a home/small business environment. Aruba InstantOn are decent as well from my experience, but they’re cloud managed and this is self-hosted after all :)

    I’ve extensively used Cisco, Meraki, Fortinet, Cambium, Aruba, Ubiquiti and Juniper in a professional setting. Avoid Fortinet and Cambium APs if you can, my experience is that they can be pretty unstable.

    Generally speaking if you’re going to have multiple APs, you’ll want something that’s centrally managed so the APs are able to be aware of each other and manage clients effectively.