Unbound 1.13.0

Unbound
1

Hi,

after upgrading unbound to version 1.13.0 (from 1.12.0) on FreeBSD running
'unbound-anchor' shows the following errors on IPv4-only hosts:

[1608235690] libunbound[16693:0] error: udp connect failed: No route to host for 2001:7fe::53 port 53
[1608235690] libunbound[16693:0] error: udp connect failed: No route to host for 2001:500:2f::f port 53
[1608235690] libunbound[16693:0] error: udp connect failed: No route to host for 2001:500:9f::42 port 53

This also happens on Arch GNU/Linux:

[1608240749] libunbound[11638:0] error: udp connect failed: Network is unreachable for 2001:500:2::c port 53
[1608240749] libunbound[11638:0] error: udp connect failed: Network is unreachable for 2001:503:ba3e::2:30 port 53
[1608240749] libunbound[11638:0] error: udp connect failed: Network is unreachable for 2001:500:2d::d port 53

2

Hi,

3

Yeah, of course i tried this, but this alone does not help.

1. unbound-anchor does not read unbound.conf unless the -C switch
(plus filename) is used. In this case I can also use -4.

2. Why does this happen with 1.13.0 and not with 1.12.0?

Thanks.

4

Hi Herbert,

Unbound 1.13.0 started using connect() on the udp sockets and this causes the extra error messages you see.

There is already code in the repo (https://github.com/NLnetLabs/unbound/commit/70776609322d4629fd1418224887470498a670e0) to silence those on low verbosity but it will be released with the next version.

Best regards,
-- George

5

This indeed fixes the issue.

Thanks.