Why didn’t IPv6 work in my home network?
33 points by gowthamgts
33 points by gowthamgts
that is terrible and adguard home should be ashamed of themselves
I don't think that setting is on by default.... Also using adguard home, and it's disabled here, and I'm quite sure I hadn't touched that (as I just replaced the config/router less than 2 weeks ago).
Why does this exist...
Because the dns Adblock communities in general (Adguard, pihole, and others) have historically had a very antagonistic relationship with IPv6 and dual-stack networks. "Disable IPv6" is still the first recommendation to any support request with these services, both from official support channels and the project communities in general out in forums, discords, and subreddits.
That's interesting... is there a documented reason?
(good thing my main home network is not dual stack (as in, NAT64-only) /jk)
My experiences have been primarily with Pi-hole and its community, but I think the dynamic is shared among many of these projects.
Dual stack networks generate a significant support burden on network services and stacks that were designed and built to operate in legacy IPv4 networks by developers who have little experience with IPv6 or dual stack. The Pi-hole community has spent years fielding support requests and user confusion that stems from DNS requests bypassing the DNS Adblocks because the blocking resolvers don't exist in the IPv6 path for DNS resolution. This means users show up and create a support burden that is trivially resolved by just instructing the users to disable IPv6 which "solves" the failure mode completely and has no immediately obvious downsides that would deter that solution.
Honestly a reasonable solution. No downside for users, significant reduction in necessary development resources.
I'd push back on the "no downside for users" assertion. There are many benefits for users and the internet as a whole to deprecate and move past legacy technologies like IPv4 and NAT, both of which are the source of considerable developer friction and unnecessary development work.
Because ipv6 is badly designed and easy to misconfigure, so the most obvious advice is to disable it.
I just debugged the inverse problem: IPv4 isn't working on my home network.
It's an IPv6-only service with DS-Lite for IPv4 connectivity. With DS-Lite, the home router tunnels IPv4 packets to a NAT at the ISP called AFTR. The domain of the AFTR is provided via DHCPv6, and is in my case of the form something.aftr.kabelbw.de. This domain currently does not resolve, as denic has some trouble with its DNSSEC configuration.
Luckily I did not disable IPv6 anywhere, so everything except github is working fine!