This is what I'm seeing:

named has failed, please contact the sysadmin (result was "named is not running").
Jul 25 11:41:56 sp2561 named: named shutdown failed
Jul 25 11:41:56 sp2561 named[6860]: starting BIND 9.2.1 -u named
Jul 25 11:41:56 sp2561 named[6860]: using 1 CPU
Jul 25 11:41:56 sp2561 named[6860]: loading configuration from '/etc/named.conf'
Jul 25 11:41:56 sp2561 named[6860]: no IPv6 interfaces found
Jul 25 11:41:56 sp2561 named[6860]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 25 11:41:56 sp2561 named[6860]: listening on IPv4 interface eth0, XX.XXX.XX.XXX#53
Jul 25 11:41:56 sp2561 named[6860]: /etc/named.conf:2: couldn't install keys for command channel 127.0.0.1#953: not found
Jul 25 11:41:56 sp2561 named[6860]: /etc/named.conf:2: couldn't add command channel 127.0.0.1#953: not found
Jul 25 11:41:56 sp2561 named[6860]: couldn't open pid file '/var/run/named/named.pid': Permission denied
Jul 25 11:41:56 sp2561 named[6860]: exiting (due to early fatal error)
Jul 25 11:41:57 sp2561 named: named startup failed
Jul 25 11:41:57 sp2561 named: named shutdown failed
Jul 25 11:41:57 sp2561 named[6893]: starting BIND 9.2.1 -u named
Jul 25 11:41:57 sp2561 named[6893]: using 1 CPU
Jul 25 11:41:57 sp2561 named: named startup succeeded
Jul 25 11:41:57 sp2561 named[6893]: loading configuration from '/etc/named.conf'
Jul 25 11:41:57 sp2561 named[6893]: no IPv6 interfaces found
Jul 25 11:41:57 sp2561 named[6893]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 25 11:41:57 sp2561 named[6893]: listening on IPv4 interface eth0, XX.XXX.XX.XXX#53
Jul 25 11:41:57 sp2561 named[6893]: /etc/named.conf:2: couldn't install keys for command channel 127.0.0.1#953: not found
Jul 25 11:41:58 sp2561 named[6893]: /etc/named.conf:2: couldn't add command channel 127.0.0.1#953: not found
Jul 25 11:41:58 sp2561 named[6893]: couldn't open pid file '/var/run/named/named.pid': Permission denied
Jul 25 11:41:58 sp2561 named[6893]: exiting (due to early fatal error)


I've tried restarting bind from the command line as well as through WHM, no luck. Any help would be greatly appreciated, thanks.

Jay

It's not shutting down properly, so the named.pid file remains open. Thus the new instance of BIND cannot open the active file... when the named.pid cannot be opened, BIND cannot be started again.

Investigation as to why BIND is not gracefully shutting down is necessary.