2023-01-27 22:43 GMT, Zack Newman <z...@philomathiclife.com>: >> Jan 27 20:59:41 nc10 unbound: [72478:0] error: udp connect failed: No >> route to host for 2001:4860:4802:36::a port 53 (len 28) >> Jan 27 20:59:41 nc10 unbound: [72478:0] error: udp connect failed: No >> route to host for 2001:4860:4802:32::a port 53 (len 28) >> Jan 27 20:59:41 nc10 unbound: [72478:0] error: udp connect failed: No >> route to host for 2001:4860:4802:32::a port 53 (len 28) > > Your problem has nothing to do with unbound(8). You have IPv6 > misconfigured on your machine, so fix that. This also explains why you > normally can resolve domains: unfortunately, IPv6 is still not that > popular which means unbound normally has no choice but to communicate > with the nameservers via IPv4 which you likely have set up correctly. > > In the meantime, set do-ip6 to no in unbound.conf(5); but don't ignore > your misconfigured IPv6 setup. There are likely other issues happening > that you don't know.
misconfigured?! I did not configure it, I never configured it. Is it necessary? I have run0 interface with an IPv4 address and connected to a home router of a neighbour. Is it not enough? Do I need also an IPv6 address on it? In any case, I did realise that the messages have to do with IPv6 and uncommented "do-ip6: no". But I suspect, that was not the problem, but rather what Stuart said. We will see. Rod.
