limit files set to fdlimit

Barry Margolin barmar at alum.mit.edu
Thu Nov 20 23:36:02 UTC 2003


In article <bpjiuh$16n$1 at sf1.isc.org>,  <bind_ml2 at telusquebec.net> wrote:
>We have bind 8.2.7-REL on a solaris 8. November 18 and 19, our DNS =
>stopped
>answering and I found the following message in the named log:
>limit files set to fdlimit (1024)
>
>I did a pfiles and saw a lot of this kind of records (something like =
>1000
>records):
>
>148: S_IFSOCK mode:0666 dev:229,0 ino:60560 uid:0 gid:0 size:0
>       O_RDWR|O_NONBLOCK FD_CLOEXEC
>        sockname: AF_INET =85
>
>I know that means too much descriptors opened but why named opens so =
>much
>Sockets?

Does your server have lots of virtual IP's configured on it?  BIND needs to
open a socket for each IP that it listens on.

If you have lots of IP's, you probably don't need DNS answering on all of
them, so you can use the "listen-on" option to tell it which ones DNS
should answer on, and it won't waste sockets on the rest.

-- 
Barry Margolin, barmar at alum.mit.edu
Level(3), Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.


More information about the bind-users mailing list