On Fri, Jul 17, 2026 at 02:06:51PM +0100, Joe wrote: > On Fri, 17 Jul 2026 11:00:22 +0000 > Andy Smith <[email protected]> wrote: > > Disabling IPv6 in one app on one machine seems like a terrible idea > > when the problem is that you have broken IPv6 on every machine in your > > network. > > > > If you can't fix the router why would you not just disable SLAAC or > > IPv6 on each machine? > > > > A lot of work seems to be being made here out of a simple problem. > > Can I ask what the advantages are to using IPv6 inside a four-computer > network?
I am baffled how you do not seem to grasp that what you have right now is BROKEN AND CAUSING PROBLEMS. Your computers think they have IPv6 and so are trying to use it. Linux chooses to use IPv6 first if it thinks it can. Since yours doesn't work, every host you connect to that has an IPv6 address in DNS introduces a delay while your computers figure out that it isn't working and retry on IPv4. I have suggested at least three times now that you disable IPv6 if you can't make it work. That would be better than having it in a broken state. It's besides the point what the advantages might be of using IPv6 on your LAN. You don't have working IPv6. What you have is a broken setup that is causing you problems every time you resolve a host that has IPv6 records in the DNS. Fix that first and think about IPv6 on the LAN later, if ever. > I thought I had said that there is probably nothing wrong with the > router There 100% is a problem with your router. It is most likely sending IPv6 autoconfig packets that cause your hosts to autoconfigure an IPv6 address by SLAAC. If it's not doing that then it is doing DHCPv6, but I think SLAAC is more likely. There is no other way for your hosts to have global scope IPv6 addresses unless you statically configured them, which you say you did not. We could tell more if you would simply show us the full output of "ip addr show", which you have also been asked for several times now. > I just don't have an IPv6 connection to the Internet, because > my ISP does not currently provide it. If your connection does not support IPv6 then it is NOT CORRECT for your router to be handing out IPv6 addresses. It is NOT EXPECTED for your hosts to have IPv6 addresses in this situation. The fact that they do is causing you problems. I don't know how to make this more clear. > When that changes, the inability of BIND9 to see the Debian server > will disappear. That has actually not been proven yet, but at this point is a bit of a tangent. > Until then, I will grudgingly use my ISP's DNS servers. That is not the issue. Any DNS resolver, including third party ones run by Google or whoever, will hand you back AAAA records (IPv6 addresses), which your hosts will try to reach if they think they have IPv6 connectivity. This happens even if you yourself do not have any IPv6 connectivity. The difference is that your apps do not try to use any AAAA record if they themselves don't have IPv6. Yours think they do, and that's a problem. You must stop your hosts from having global scope IPv6 addresses if IPv6 is not going to work. They WILL try to use them otherwise. BTW, making bind9 use only IPv6 will not stop it handing back AAAA records in answers, so other software on your network will still encounter problems if it's using your bind9 server as a resolver. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
