You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first log output uses 192.0.2.3/32 because that is the listening interface. Default refuse access control is happening per listening interface. (Other access control actions can also be configured per interface as well).
The second log output uses 0.0.0.0/0 because this is a configured client network space; configured client networks have priority over listening interfaces.
The first log output can be misleading if you don't know how Unbound applies ACLs.
Would an output like the one below make things more clear?
unbound: [607563:0] debug: refused query from 198.51.100.15 port 9987 because of 192.0.2.3/32 (interface) refuse
When a server on example IP 192.0.2.3 has
access-control
defined e.g. like this:and it receives a query from a different address, say 198.51.100.15, unbound will log:
This is misleading. The true reason is "because the default access control rule is to refuse".
If I add
after the above
allow
, then the log is correct:System:
unbound -V
output:The text was updated successfully, but these errors were encountered: