Hi Andreas,
These things work fine when I try to dig at IPv4 or IPv6 addresses. Also
valgrind notices no problems with the printout code. What makes it go
wrong for you? What are the interface: options?
It works for me with interface: IPs, localhost, interface-automatic, by
interface name, wildcard IP. I wonder what causes the issue.
Perhaps this is more of a bug fix for a future release. The rc1 sequence
is mostly meant for bugs that hamper deployment, package management
trouble. But it is good to fix, to have a fix for it.
Best regards, Wouter
On 12/03/2024 22:17, A. Schulze via Unbound-users wrote:
Am 11.03.24 um 19:16 schrieb A. Schulze via Unbound-users:
Unbound 1.19.3rc1 pre-release is available:
forgot to mention: 1.18.3rc1 is running here since then without noise
or trouble ...
well, just noticed strange logging.
- I've enabled "log-destaddr: yes"
- unbound listen on a specific IPv4 and IPv6 address
- 'kdig -4 . @ipv4 SOA' produce expected logging like this:
reply: 192.0.2.1 . SOA IN NOERROR 0.000000 1 92 on udp 192.0.2.53 53
- 'kdig -6 . @ipv6 SOA' produce this:
reply: 2001:db8::1 . SOA IN NOERROR 0.000000 1 92 on udp 53
or
reply: 2001:db8::1 . SOA IN NOERROR 0.000000 1 92 on udp . 53
or even
reply: 2001:db8::1 . SOA IN NOERROR 0.000000 1 92 on udp �7
< 53
looks like there will be an rc3?
Andreas
