On 27.02.13 17:32, Marco C. Coelho wrote:
Mark Andrews was right.
This server was being hammered so hard that logging the rejects was
killing the performance.
adding:
logging {
category default { null; };
//category lame-servers { null; };
};
to named.conf fixed the performance issues.
You
In message <512e97aa.2020...@argontech.net>, "Marco C. Coelho" writes:
> Just so the list has the same answer,
>
> Mark Andrews was right.
> This server was being hammered so hard that logging the rejects was
> killing the performance.
> adding:
> logging {
>category default { null; };
>
> From: "Marco C. Coelho"
> Mark Andrews was right.
> This server was being hammered so hard that logging the rejects was
> killing the performance.
> adding:
> logging {
>category default { null; };
>//category lame-servers { null; };
> };
> On 2/27/2013 5:18 PM, Mark Andrews wrote:
>
Just so the list has the same answer,
Mark Andrews was right.
This server was being hammered so hard that logging the rejects was
killing the performance.
adding:
logging {
category default { null; };
//category lame-servers { null; };
};
to named.conf fixed the performance issues.
mc
On
I suspect this is just logging. send the security channel to null;
for a while. Once your server gets off the I'm a recursive reflector
lists you can turn it on again.
In message <512e7940.7060...@argontech.net>, "Marco C. Coelho" writes:
>
> I discovered my bind 9 server was being used in a DD
I discovered my bind 9 server was being used in a DDOS attack so I
decided (late) to block outside networks from making recursive
requests. The problem is every time I enable this, the time for DNS
queries goes from 0-1ms to 2000-6000ms or just times out completely.
The options section is b
6 matches
Mail list logo