> > What exactly does "slow down" mean here? Are you missing messages in
> > the log files? Or are requests not answered in a timely fashion?
> >
>
> "slow down" means an increment in the time consumed by bind to answer a
> query.
> "heavy load" means about 20 millions query / day per machine, wit
2016-12-07 8:27 GMT+01:00 Peter Rathlev :
> stores _everything_, including debug messages from "execute", you might
> want "Storage=volatile" there as well. You probably already have
>
thanks, i missed this volatile thing
> What exactly does "slow down" mean here? Are you missing messages in
>
On Tue, 2016-12-06 at 13:23 +0100, Ivan Fabris wrote:
> I set up some dns logging to syslog ( rsyslog actually ), which
> forwards local1.* and local2.* to a remote rsyslog
[...]
> Both syslog, and journalctl, have all the rate limits set to infinite
> ( all that I could find )
Urgh..
Hi,
I set up some dns logging to syslog ( rsyslog actually ), which forwards
local1.* and local2.* to a remote rsyslog
channel csyslog_d {
syslog local1;
severity debug 3 ;
print-time yes;
print-category yes;
print-severity yes;
};
channel rpz_d {
syslog local2
Hi
Thanks for good answers, I now know what to do and how to proceed.
Thanks.
On 30/05/12 13:17, Matus UHLAR - fantomas wrote:
> On 30.05.12 12:16, Sten Carlsen wrote:
>> I was considering to use the syslog on a different host for logging from
>> bind. The purpose was to collect logs from vario
On 30.05.12 12:16, Sten Carlsen wrote:
I was considering to use the syslog on a different host for logging from
bind. The purpose was to collect logs from various places into one
repository.
[...]
Can bind send its logging output to an external syslog?
Not directly. However, that is what sysl
I think the normal way to do this is run a syslog server on the host
running bind, which is configured to just forward all log messages to
the remote syslog server. Otherwise, bind would have to implement the
syslog network protocol(s) itself, rather than just use the system
standard local syslog f
On 30/05/2012 11:16, Sten Carlsen wrote:
Hi
I was considering to use the syslog on a different host for logging
from bind. The purpose was to collect logs from various places into
one repository.
This is not a busy installation so performance is not expected to be a
problem.
I looked in t
It's syslogd's job to relay messages to other servers. You
need to configure syslogd to do this for named.
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
__
Sten
The syslog daemon on the machine where BIND runs on will send the syslog
messages to the central syslog server. So you need to configure your
syslog.conf file to send the facility that BIND uses, normaly daemon, to
the remote syslog server.
The syslog.conf on Solaris looks something lik
Hi
I was considering to use the syslog on a different host for logging from
bind. The purpose was to collect logs from various places into one
repository.
This is not a busy installation so performance is not expected to be a
problem.
I looked in the arm but could not see where I could put the I
11 matches
Mail list logo
