On Mon, Sep 21, 2026 at 12:25 PM CGS <[email protected]> wrote: > > On 2026-09-21, Joe <[email protected]> wrote: > > > > [...] > > > > Short version: my ISP does not (yet) provide IPv6 connectivity, and my > > router was supplied by the ISP so already had IPv6 disabled. I was > > having trouble with DNS failures due to bind9 not finding an IPv6 > > route out of the network and giving up, even though the requested host > > also had an IPv4 address. > > > > I was advised that disabling IPv6 in the kernel was the final fix, > > so I did that to the two Raspberry Pis which were having the problems, > > mostly of finding RPi apt repositories. No good. I had to disable it > > individually in both bind9 and apt to get reliable IPv4 lookups. I left > > the thread at this point. > > IPv6 seems to be the future, so I guess these problems will eventually > fade away, although the OP has been struggling since 2015 (!), > apparently, which is a testament to something.
I would probably qualify that with, IPv6 is the future of _The Internet_. My local intranet will likely stay IPv4 for the remainder of my life, because it is easy for me to manage 192.168/16. I know the router is 192.168.1.1 (/24 mask at the router). The DHCP server behind my pfSense firewall hands out addresses starting at 172.16.4.1 (/12 mask). I couldn't care less what Verizon is doing with its infrastructure and my router. I don't control it, so I don't waste any time on it. Jeff
