Dear Voxel,
After upgrade unbound to the most recent version (1.13.0) there are issues with accessing domain 'internic.net'.
unbound-host -C /opt/etc/unbound/unbound.conf -v -d internic.net. -t SOA
internic.net. has SOA record sns.dns.icann.org. noc.dns.icann.org. 2020121130 3600 1800 604800 3600 (BOGUS (security failure))
validation failure <internic.net. SOA IN>: No DNSKEY record for key internic.net. while building chain of trust
There are many "Operation not supported" in unbound log before getting above error 'No DNSKEY record'.
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 199.4.138.53 port 53
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 192.82.133.30 port 53
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 192.82.133.30 port 53
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 192.42.178.30 port 53
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 192.42.178.30 port 53
Jan 17 22:51:49 libunbound[18715:0] info: Capsforid: timeouts, starting fallback
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 192.42.177.30 port 53
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 192.42.177.30 port 53
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 202.12.31.53 port 53
Is it possible to get access to previous version(1.11.0) while investigating?
Do you know what problem could be?
There is new feature: "upstream TCP and TLS query reuse".
NLnet Labs - Unbound - Download
Thanks,
After upgrade unbound to the most recent version (1.13.0) there are issues with accessing domain 'internic.net'.
unbound-host -C /opt/etc/unbound/unbound.conf -v -d internic.net. -t SOA
internic.net. has SOA record sns.dns.icann.org. noc.dns.icann.org. 2020121130 3600 1800 604800 3600 (BOGUS (security failure))
validation failure <internic.net. SOA IN>: No DNSKEY record for key internic.net. while building chain of trust
There are many "Operation not supported" in unbound log before getting above error 'No DNSKEY record'.
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 199.4.138.53 port 53
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 192.82.133.30 port 53
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 192.82.133.30 port 53
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 192.42.178.30 port 53
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 192.42.178.30 port 53
Jan 17 22:51:49 libunbound[18715:0] info: Capsforid: timeouts, starting fallback
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 192.42.177.30 port 53
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 192.42.177.30 port 53
Jan 17 22:51:49 libunbound[18715:0] error: tcp sendmsg: Operation not supported for 202.12.31.53 port 53
Is it possible to get access to previous version(1.11.0) while investigating?
Do you know what problem could be?
There is new feature: "upstream TCP and TLS query reuse".
NLnet Labs - Unbound - Download
Thanks,