This is for one of our masters which has about 20K zones and handles zone
transfer traffic from few hundred of our slaves.
On Thursday, October 16, 2014 2:27 PM, Barry Margolin
<[email protected]> wrote:
In article <[email protected]>,
Shawn Zhou <[email protected]> wrote:
> Hello,
> While I was investigating potential SYN flooding warning messages on my Linux
> box for our DNS traffic,I was very surprised to see the backlog was set to
> very small numbers for BIND tcp sockets.
> strace showed backlog was '10' for listening socket for port 53 and '128' for
> listening socket for port 953 (rdnc traffic).
> I've restarted BIND after I updated somaxconn but BIND didn't pick up the
> value.
> Why doesn't BIND set the backlog to a huge number and let OSes reduce it to
> whatever somaxconn is? Or just set backlog to whatever is is set for
> somaxconn?
Since TCP queries should be infrequent, why does it need a high backlog?
It seems like it's already increasing it, IIRC the default is 5.
--
Barry Margolin
Arlington, MA
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/bind-users
