Failing to start named with BIND 9.1.1

[Jim Reid]

>>>>> "Alecio" == Alecio Maduro <alecio at cura.net> writes:

    Alecio> Hi,

    Alecio> I just upgraded from BIND 4.9.7 to BIND 9.1.1.  In order
    Alecio> to test that everything was ok, I first made the changes
    Alecio> to the secondary DNS servers and tested this out by
    Alecio> killing the Primary DNS Server and everything seems
    Alecio> ok. The only message received so far on the secondary
    Alecio> server has been "named[18647]:<3.3> client XXX.XXX.XXX.XXX
    Alecio> #137: no matching view in class 'CLASS256' ".  Btw. what
    Alecio> does this message mean ?  

It means you've not checked the list archives at www.isc.org. This
question has been asked and answered many times. You have a broken
client asking for queries in an undefined class, probably some idiot
WINS box.

    Alecio> named[8029]:<3.3> creating IPv4 interface loop35 failed; interface ignored .  .  .  
    Alecio> named[8029]:<3.2> couldn't open pid file '/var/run/named.pid': Too many open files 

    Alecio> The configuration is as follows: The Primary DNS Server is
    Alecio> also a WEB Server which uses virtual IP numbers for the
    Alecio> different WEB Sites.  These are the loop0 to loop36.
    Alecio> dpen0 is the ethernet interface. 

These error messages seem fairly clear. The name server is trying to
use more file descriptors than the OS allows. Either configure the OS
to let the name server use more file descriptors or get the name
server to use less of them. The BIND[89] name servers will create 2
sockets for each network interface by default: one for UDP and one for
TCP queries. So if you have lots of (virtual) network interfaces...you
can do the arithmetic. You could use the listen-on option to make the
name server only listen for queries on the system's real network
interfaces. It's unlikely anything will ever send DNS queries to the
virtual interfaces, so why bother having listeners on them?