> -Original Message-
> From: Plhu [mailto:p...@seznam.cz]
> a few simple ideas to your tests:
> - have you inspected the per-thread CPU? Aren't some of the threads
> overloaded?
I've tested both the auto-calculated values (one thread per available core) and
explicitly overridden this
> -Original Message-
> From: Mathew Ian Eis [mailto:mathew@nau.edu]
>
>
> Basically the math here is “large enough that you can queue up the
> 9X.XXXth percentile of traffic bursts without dropping them, but not so
> large that you waste processing time fiddling with the queue”. Sin
BIND has no way of differentiating these queries, since reverse-lookup queries
aren't "special".
But certainly, if you syslog rather than writing directly to a file, there are
syslog daemons that can filter, based on regex'es and the like.
In message
<88ef58f000ec4b4684700c2aa3a73d7a08180abd2...@w2008dc01.colliniconsulting.lan>,
Job writes:
> Dear guys,
>
> is there a way in Bind 9 to stop logging (to bind.log standard file) all the
> in-addr.arpa queries?
> We would like to log everything else but not the reverse resolution que
Howdy Stuart,
> Re: net.core.rmem - I'd love to figure out what the math here should be. 'X
> number of simultaneous connections multiplied by Y socket memory size = rmem'
> or some such.
Basically the math here is “large enough that you can queue up the 9X.XXXth
percentile of traffic bursts
Tried empty-zones-enable yes; in named.conf?
On Thu, Jun 1, 2017 at 10:28 AM, Job wrote:
> Dear guys,
>
> is there a way in Bind 9 to stop logging (to bind.log standard file) all the
> in-addr.arpa queries?
> We would like to log everything else but not the reverse resolution queries.
>
> Thank
Dear guys,
is there a way in Bind 9 to stop logging (to bind.log standard file) all the
in-addr.arpa queries?
We would like to log everything else but not the reverse resolution queries.
Thank you!
F
___
Please visit https://lists.isc.org/mailman/listi
Hello Stuart,
a few simple ideas to your tests:
- have you inspected the per-thread CPU? Aren't some of the threads overloaded?
- have you tried to get the statistics from the Bind server using the
XML or JSON interface? It may bring you another insight to the errors.
- I may have missed the
Cheers Matthew.
1) Not seeing that error, seeing this one instead:
01-Jun-2017 01:46:27.952 client: warning: client 192.168.0.23#38125
(x41fe848-f3d1-4eec-967e-039d075ee864.perf1000): error sending response: would
block
Only seeing a few of them per run (out of ~70 million requests).
Whilst
9 matches
Mail list logo
