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!
Do you not run a firewall? Because your concerns are 100% fixed with a statefull firewall.
I think I worded this poorly. My point about being individually routable is that, that’s the only benefit IPv6 seems to have. Unless I’m missing something.
Or, just completely bypass any config by simply not using IP6 for an environment where it offers no advantage
I’d rather not perpetuate the 30 year mistake NAT has truely become.