Crashing BIND 9.2.3 on W2K - leaves no clues

Scott MacLean scottNO at SPAMnerosoft.com
Mon Dec 1 05:46:33 UTC 2003


I have two 9.2.3 installations on W2K server boxes, one primary (master to
about 100 domains) and one secondary (slave to the master for the domains).

The master runs fine.

The slave, using virtually identical conf files (except for what requires it
to run as a slave) crashes every few minutes for no reason. Setting up debug
level logging shows nothing - it's operating fine one moment, the next it is
starting up again (I have the service set to restart).

Running named -f shows nothing - no output to screen, it functions fine for
a couple minutes, then returns gracefully with no console output as BIND
crashes to a halt.

I'm tearing my hair out over this. Anyone have any ideas?

My named.conf file:

# Start of named.conf

options {
  directory "\winnt\system32\dns\etc\namedb";           // Working directory
  pid-file "named.pid";              // Put pid file in working dir
  allow-query { any; };              // This is the default
  recursion yes;                     // Provide recursive service
  allow-notify { (master's IP); };
  allow-transfer { (master's IP); };
  listen-on {
    (slave's IP);
    127.0.0.1;
  };
};

logging {
  channel "namedlog" {
    #file "\winnt\system32\dns\etc\logfile.txt" versions 4 size 5M;
    null;
    severity debug;
    print-category yes;
    print-severity yes;
    print-time yes;
  };
  channel default_syslog {
    syslog daemon;
    severity warning;
  };
  category client         { namedlog; };
  category config         { default_syslog; namedlog; };
  category default        { default_syslog; namedlog; };
  category dnssec         { namedlog; };
  category general        { namedlog; };
  category lame-servers   { namedlog; };
  category network        { namedlog; };
  category notify         { namedlog; };
  category queries        { namedlog; };
  category resolver       { namedlog; };
  category security       { namedlog; };
  category update         { namedlog; };
  category xfer-in        { namedlog; };
  category xfer-out       { namedlog; };
};

controls {
      inet 127.0.0.1 port 953
              allow { 127.0.0.1; } keys { "rndc-key"; };
};
// Root server hints
zone "." { type hint; file "root.hint"; };

// Provide a reverse mapping for the loopback address 127.0.0.1
zone "0.0.127.in-addr.arpa" {
     type master;
     file "localhost.rev";
     notify no;
};

## Zones follow below
zone "example1.com" {
     type slave;
     masters { (master's IP); };
     file "DB.example1.com.txt";
};

zone "example2.com" {
     type slave;
     masters { (master's IP); };
     file "DB.example2.com.txt";
};




More information about the bind-users mailing list