one remaining error message in named log startup messages

Chris Buxton chris.p.buxton at
Tue Nov 16 17:36:41 UTC 2010

On Nov 15, 2010, at 6:50 AM, Tony Finch wrote:

> On Fri, 12 Nov 2010, Stewart Dean wrote:
>>      "adjusted limit on open files from 1024 to 1048576"
>> The named service works just fine.........
>> which says to add a line:
>>      named soft nofile 4096
>> to /etc/security/limits.conf
>> Did that, then tried both restarting named and rebooting the machine, but it
>> doesn't make a difference.
> Try upping it from 4096 to 1048576, since that is what BIND wants the
> limit to be.

No, the problem is that you found a Gentoo answer to a CentOS problem.

Your issue is that the operating system is by default allowing named to own no more than 1024 open file handles. This affects files as well as sockets. You want a much higher number, such as 65536 or more. The 1048576 value is simply a nice large binary number (2^20) that will definitely be large enough.

To set the limit for your operating system (as opposed to Gentoo Linux), you'll need to find the correct command for CentOS. Or you could just let named do it itself, as it does currently - the log message causes no harm and does not represent an error.

Chris Buxton
BlueCat Networks

More information about the bind-users mailing list