On Tue, 8 Sep 2026 22:22:18 +0200 Nicolas George <[email protected]> wrote:
> Joe (HE12026-09-08): > > If both are apparently available, yes. But if one is disabled in the > > kernel, it doesn't make much sense to try it at all, does it? > > And how do you think applications know that IPv6 is disabled in the > kernel? Do you suggest somebody who disables IPv6 in the kernel should > rebuild all applications with `./configure --disable-ipv6`? > > Applications know that IPv6 is disabled by trying it. cat /proc/sys/net/ipv6/conf/*/disable_ipv6 or individually per interface. > > > Dig found it fairly easily using the router's resolver, which I try > > to avoid doing, but couldn't find it at all using bind. It took me > > a while to realise that bind was only trying IPv6, and definitely > > not falling back to IPv4. But it was working properly for > > everything else, just that one repository, which definitely did > > have an IPv4 address. A suitably IPv6-disabled bind now finds it > > easily. > > Too bad you did not dig (pun intended) deeper to determine why bind > did not find the IPv4. We will never know what the real issue was. > It was a recent installation. What reason might it have for only trying IPv6? I added an option to disable it, there were no options set which prevented IPv4 from being used. -- Joe
