On 2023-01-27, Rodrigo Readi <hru...@gmail.com> wrote:
> 2023-01-27 7:09 GMT, Otto Moerbeek <o...@drijf.net>:
>> On Fri, Jan 27, 2023 at 01:26:10AM +0000, Rodrigo Readi wrote:
>>
>>> It still happens. But when I kill unbound and start it again, then
>>> resolves domains that previously did not resolve.
> ...
>>
>> Increase log level and look at the logs? Otherwise it's just a
>> guessing game.
>
> Just done, when it stops resolving I will see the messages and also try with
> "unbound-control lookup". But even if it resolves, I am getting repeatealy the
> messages:
>
> 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)
That's expected, unbound attempts to use IPv6 unless you set "do-ip6: no".
do-ip6: <yes or no>
Enable or disable whether ip6 queries are answered or issued.
Default is yes.
If you know you have no IPv6 support on your network, you can either
disable do-ip6, or reduce the log level so you don't see those messages.
--
Please keep replies on the mailing list.
