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!
Well…
Ipv6 is needed for peer to peer networks, easier for vpn and full mndgoru if you want to have a vps…
With it, you can avoid Cgnats and home Nats and usually it is faster and more reliable than ipv4.
So, see it for yourself…
Every time I try to use Ipv6, I run into dozens of weird issues and bugs and my selfhosted stuff becomes unusable/unreliable.
I don’t know where the issue exactly lies in the chain of networking, but it sure is annoying as a motherfucker to debug. As far as I can tell none of my stuff is the problem and the issue lies either with my ISP or VPS provider.
For now, I removed the AAAA entries and suddenly everything works without any hiccups. Wake me up when those issues are solved… maybe in 10 or 20 years…