Am 13.03.24 um 12:36 schrieb A. Schulze via Unbound-users:
Am 13.03.24 um 10:47 schrieb Wouter Wijngaards:
These things work fine when I try to dig at IPv4 or IPv6 addresses. Also
valgrind notices no problems with the printout code.
Hello Wouter,
I'll prepare a more simplified setup an try to make it reproducable. But this
may take some time.
Maybe there is an glitch on my side (unrelated to unbound) an I miss
interpreted my logs...
I use unbound on a host with numerous ipv6 addresses assigned per router
advertisements.
# ip a s dev eth0 | grep stable-privacy
inet6 fd00::53:38d0:4790:88ae:64b2/64 scope global dynamic mngtmpaddr
stable-privacy
example unbound.conf:
server:
interface: fd00::53:38d0:4790:88ae:64b2
access-control: fd00::/8
chroot: ""
do-daemonize: no
logfile: ""
log-destaddr: yes
log-replies: yes
log-tag-queryreply: yes
log-time-ascii: yes
pidfile: ""
# unbound -c unbound.conf
Mar 14 20:55:11 unbound[7:0] notice: init module 0: subnetcache
Mar 14 20:55:11 unbound[7:0] notice: init module 1: validator
Mar 14 20:55:11 unbound[7:0] notice: init module 2: iterator
Mar 14 20:55:11 unbound[7:0] info: start of service (unbound 1.19.3).
<in an other terminal, same host>: dig @fd00::53:38d0:4790:88ae:64b2 . soa
Mar 14 20:55:36 unbound[7:0] reply: fd00::53:38d0:4790:88ae:64b2 . SOA IN
NOERROR 0.067414 0 103 on udp ��� 53
Andreas
