unbound refuses all requests

[Johannes B. Kernel]

Sorry the confusion.... the 'module-config' was commented out....
Uncommented unbound dont starts with that config
but it was my understanding of the link above with the unbound.conf on git

best regards
marko

Am Fr., 12. Nov. 2021 um 10:45 Uhr schrieb George Thessalonikefs via
Unbound-users <unbound-users at lists.nlnetlabs.nl>:

> Hi Johannes,
>
> I see a lot of configuration errors WRT redis in your unbound.conf.
> Instead of me going over everything I would suggest to read the "Cache
> DB Module Options" section in the unbound.conf man page (Also online for
> the latest version:
> https://www.nlnetlabs.nl/documentation/unbound/unbound.conf/) as I
> believe it covers all the steps and configuration you need to make.
>
> If you still have questions feel free to ask them here again.
>
> Best regards,
> -- George
>
> On 11/11/2021 17:42, Johannes B. Kernel via Unbound-users wrote:
> > @hauke , damn  ps aux showed me 2 running daemons.....
> > and i found out, i "missed" to copy over the access.conf in
> > unbound.conf.d/  :-)
> >
> > now nearlyall is running fine..
> > only redis seems not to cache.....
> >
> > my unbound.conf.
> >
> > server:
> >
> > statistics-cumulative: yes
> > extended-statistics: yes
> > log-queries: yes
> > log-servfail: yes
> > verbosity: 3
> > val-log-level: 2
> > auto-trust-anchor-file: /etc/unbound/var/root-anchors.txt
> >
> > interface: 127.0.0.1
> > interface: 192.168.100.250
> > interface: 192.168.120.251
> > interface: 192.168.110.250
> >
> > outgoing-interface: 192.168.100.250
> > outgoing-interface: 192.168.110.250
> > outgoing-interface: 192.168.120.251
> > outgoing-interface: 116.202.87.165
> >
> > num-threads: 8
> >
> > include: /etc/unbound/unbound.conf.d/access_options.conf
> > include: /etc/unbound/unbound.conf.d/name_solving.conf
> > include: /etc/unbound/unbound.conf.d/privacy_options.conf
> > include: /etc/unbound/unbound.conf.d/cache_options.conf
> > include: /etc/unbound/unbound.conf.d/dnssec_options.conf
> > include: /etc/unbound/unbound.conf.d/blacklist.conf
> > include: /etc/unbound/unbound.conf.d/local_names.conf
> > include: /etc/unbound/unbound.conf.d/opennic_names.conf
> > include: /etc/unbound/unbound.conf.d/forwarders.conf
> >
> > remote-control:
> >        control-enable: yes
> >
> > cachedb:
> >    backend: "testframe"
> >    secret-seed: "default"
> >    redis-server-host: 127.0.0.1
> >    redis-server-port: 6379
> >    redis-timeout: 100
> >    redis-expire-records: no
> >
> >
> >
> > when i connect my redis server via "redis-cli" .....
> >
> > supabunka/etc/unbound #redis-cli
> > 127.0.0.1:6379 <http://127.0.0.1:6379>> keys *
> > (empty array)
> > 127.0.0.1:6379 <http://127.0.0.1:6379>>
> >
> >
> > seems nothing get cached......
> >
> > any idea?
> >
> >
> > Am Mi., 10. Nov. 2021 um 18:29 Uhr schrieb Hauke Lampe via Unbound-users
> > <unbound-users at lists.nlnetlabs.nl
> > <mailto:unbound-users at lists.nlnetlabs.nl>>:
> >
> >
> >     On 10.11.21 17:50, Johannes B. Kernel via Unbound-users wrote:
> >
> >      > and now it works, for 3-5 requests, the all gets refused for 2-5
> >     time, then
> >      > again it works .............
> >      >
> >      > Nov 10 17:45:40 supabunka unbound: [25308:1] debug: refused query
> >     from ip4
> >      > Nov 10 17:45:43 supabunka unbound: [15016:0] info:
> >     192.168.100.250 heise.de <http://heise.de>.
> >
> >     The refusals come from PID 25308 while PID 15016 processes the
> requests.
> >
> >     Do you have multiple daemons with different configurations and/or a
> DNS
> >     balancer?
> >
> >
> >     Hauke.
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20211112/19e3a366/attachment.htm>