> On 18 Aug 2016, at 15:46, Andrew Deason wrote:
>
> On Wed, 17 Aug 2016 12:23:15 +1000
> teor wrote:
>
>> Has anyone checked if the logs on other resolvers (like unbound) have
>> the same issue?
>
> On my exit running unbound, I haven't seen any messages from unbound
> beyond the startup/shu
On Wed, 17 Aug 2016 12:23:15 +1000
teor wrote:
> Has anyone checked if the logs on other resolvers (like unbound) have
> the same issue?
On my exit running unbound, I haven't seen any messages from unbound
beyond the startup/shutdown messages for the past several weeks, but
maybe I just haven't
I couldn't find the default config for Unbound when I installed it, so I
just used the example file. Logging is disabled by default in this file.
Unbound has a setting for "log-queries" which will print a line with time,
IP, name, type, and class for each query. Not sure if setting this to "no"
wil
On 8/16/16, teor wrote:
> Or is it safer just to log a few essential categories?
> (Can anyone recommend any?)
Once properly set up and tested, DNS just works, only
maintenance being updating root zone or keys whenever.
You might be interested in aggregated stats logs it emits,
memory, queries pe
Hi,
When I set up a Tor Exit, I set up a local resolver (BIND) as a cache.
Today, I was monitoring the syslog, and I noticed that BIND logs DNS names when
resolution fails.
(I have since removed these entries from the logs.)
One way to prevent this is to disable logging on BIND entirely:
loggin
