submitted 17 hours ago by ogy@fedia.io to c/selfhosted@lemmy.world

21 comments fedilink hide all child comments

I've been setting up my first nas and set up DNS routing from my router to adguard home, which then routes traffic to nginx-proxy-manager, which then routes to the docker container for the intended service. I've spent days pulling my hair out, trying to figure out what the issue was - why all my services behind NPM were periodically unreachable on my browser. after a wifi reset on my laptop they'd come back online, but why? today I found out that although my router correctly had the DHCP setting correctly set up to route IPv4 traffic to adguard, there was a separate section in the router settings that handles IPv6 settings, and that this was set up to look for my ISP's assigned DNS provider. Just posting on the off chance anyone finds this helpful or entertaining. I am extremely tired (I have a 3 month old baby) so please bare with the poor formatting of the post!

you are viewing a single comment's thread
view the rest of the comments

[-] Onomatopoeia@lemmy.cafe -1 points 13 hours ago

Or, just completely bypass any config by simply not using IP6 for an environment where it offers no advantage

[-] slazer2au@lemmy.world 9 points 13 hours ago

I'd rather not perpetuate the 30 year mistake NAT has truely become.

[-] ogy@fedia.io 1 points 6 hours ago

I ended up having to. I'd have liked to keep IPv6 on, but my router wasn't letting me permanently route the IPv6 traffic to my nas. something about my ISP using dynamic addresses so it would change periodically, and the router wouldn't accept the format of IP addresses that I generated.

[-] cmnybo@discuss.tchncs.de 1 points 5 hours ago

Some ISPs just have a broken IPv6 implementation. If they do it correctly, they should delegate a /56 prefix that doesn't change unless the DUID on your router changes or your PoP changes.

this post was submitted on 19 Aug 2026

43 points (97.8% liked)

Selfhosted

61544 readers

752 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