Query log coverage

Darren S. phatbuckett at gmail.com
Thu May 16 20:02:40 CEST 2019


On Mon, May 13, 2019 at 6:51 AM Wouter Wijngaards via Unbound-users <
unbound-users at nlnetlabs.nl> wrote:

> Hi Darren,
>
> On 5/7/19 12:09 AM, Darren S. via Unbound-users wrote:
> > Is there a simple way in Unbound to output a query log for each client
> > query to the resolver? Looking for:
> >
> > - All cache hits
> > - All cache misses
> > - Inclusion of client IP address and query source port
> >
> > Was looking at `verbosity` option but understood it to indicate that
> > only level 5 logs client info, and only cache misses in that case. I
> > have a very low volume deployment and the overhead of query logging
> > shouldn't be an issue, but it would be ideal if we didn't have to deal
> > with level 5 logging in the output.
> >
> > Hoping to avoid dnstap for now as would prefer to stay with native OS
> > package and no additional dependencies.
>
> Yes this feature exists already.  In fact a number of config statements.


Wonderful! Thanks for reviewing the options. I think I had a different
understanding of how the log verbosity was implemented.

-- 
Darren Spruell
phatbuckett at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://nlnetlabs.nl/pipermail/unbound-users/attachments/20190516/de91295d/attachment.html>


More information about the Unbound-users mailing list