Hi Johannes,
Unbound by default only listens on localhost.
You would need to configure 'access-control:' to allow client netblocks
to query Unbound.
From your example I guess that something like
access-control: 192.168.0.0/16 allow
would allow most of your clients to connect.
Best regards,
-- George
On 10/11/2021 16:39, Johannes B. Kernel via Unbound-users wrote:
hello list,
unbound refuses all requests on my machine.
google dns server works fine, tested already.
my unbound.conf looks like:
server:
statistics-cumulative: yes
extended-statistics: yes
log-queries: yes
log-servfail: yes
verbosity: 9
val-log-level: 2
interface: 192.168.100.250
interface: 116.202.87.165
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: 2
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
can anyone help with am idea?
best regards
marko
