On Mon, Jan 25, 2021 at 08:56:36PM +0100, Klemens Nanni wrote: > On Mon, Jan 25, 2021 at 07:05:40PM +0100, Florian Obser wrote: > > Unwind / libunbound goes pretty badly off the rails when an address > > family is not available, it still tries to talk to nameservers with an > > unreachable address family. > > I don't think it's libunbound's place to figure this out. It can't > > sensibly do a getifaddrs on every query... > > So let's help it out a bit. > Cool, this is pretty much what I had in mind after your reply to the > other thread. > > Have you tested this by adding some IPv4 address? unwind dies on me: > > $ ifconfig all inet | grep -w inet > inet 127.0.0.1 netmask 0xff000000 > $ doas ifconfig tun0 1.2.3.4 > > check_available_af 3 - 2 > fatal in resolver: new_resolver: invalid resolver state: dead > frontend exiting > waiting for children to terminate > terminating >
This has been fixed, and it was indeed unreleated to this diff. We also need to restart dead resolvers when we restart all resolvers because of a config change in libunbound. (e.g. changing of log level or new trust anchors). -- I'm not entirely sure you are real.
