hey stuart,
I suspect it's my hardware.When I copy the exact config to another
machine and enable num-threads on both machines, i get two different
behaviours.
On my main system I get cache issue, on its backup there is no cache
issue. Both machines have the exact same installation and etc. I then
tried a third machine
and sure enough config works no cache issues. You may close this bug
report, clearly a user issue.
I had both machines running the following config:
# Remote control config section.
remote-control:
# Enable remote control with unbound-control(8) here.
# set up the keys and certificates with unbound-control-setup.
control-enable: yes
# Set to no and use an absolute path as control-interface to use
# a unix local named pipe for unbound-control.
control-use-cert: no
server:
interface: 127.0.0.1@53
interface: 192.168.1.54@53
interface: ::1
access-control: 127.0.0.0/8 allow
access-control: ::1 allow
access-control: 192.168.0.0/16 allow
access-control: 0.0.0.0/0 refuse
access-control: ::0/0 refuse
root-hints: "/var/unbound/etc/root.hints"
hide-identity: yes
hide-version: yes
do-ip4: yes
do-ip6: no
do-udp: yes
do-tcp: yes
num-threads: 2
# Use an upstream forwarder (recursive resolver) for specific zones.
# Example addresses given below are public resolvers valid as of 2014/03.
#
forward-zone:
name: "." # use for ALL queries
forward-addr: 1.1.1.1@53
On Tue, Apr 27, 2021 at 12:36 PM Stuart Henderson
wrote:
> On 2021/04/27 11:15, Amado Tucker wrote:
> > Hello world,
> > when I utilize num-threads in unbound and I set the num-threads options
> to
> > any number other than 1 or if num-threads is commented out, unbound in
> > memory dns cache stops working.
>
> This surprised me so I tested on my servers, it works as expected here
> on -current (unbound 1.13.1) or 6.8 (1.11.0), both amd64, with either no
> num-threads, or set to 1/2/4.
>
> Perhaps something else in your config is triggering it?
>
>
