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
On 18/12/2020 17:35, Herbert J. Skuhra via Unbound-users wrote:
On Fri, 18 Dec 2020 03:25:02 +0100, Xavier Belanger wrote:
Hi,
"Herbert J. Skuhra via Unbound-users" wrote:
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:
(...)
If your server is IPv4 only, using the following configuration
should solve that issue:
# Enable IPv6, "yes" or "no".
do-ip6: no
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.
--
Herbert
