I've done something a while back that has messed with my named.conf and prevents me from restarting named service normally... My problem... # service named restart Stopping named: [FAILED] Starting named: named: already running [FAILED] nothing gets logged in /var/log/messages obviously, I can do this to restart it... [root at srv1 etc]# ps aux|grep named named 26598 0.1 0.3 72168 3732 ? Ssl 15:41 0:00 /usr/sbin/named -u named -4 -t /var/named/chroot root 26687 0.0 0.0 3880 696 pts/18 S+ 15:43 0:00 grep named [root at srv1 etc]# kill 26598 [root at srv1 etc]# service named restart Stopping named: [FAILED] Starting named: [ OK ] and the pid of named seems to be where it belongs... # ls -l /var/named/chroot/var/run/named/named.pid -rw-r--r-- 1 named named 6 Sep 21 15:43 /var/named/chroot/var/run/named/named.pid if I try... # service named status rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. but looking at my named.conf, I'm directly including rndc.key # grep rndc named.conf inet 127.0.0.1 allow { localhost; } keys { DYNAMIC_DNS_KEY; rndc.key; }; include "/etc/rndc.key"; and obviously, I am running named-chroot... # tail -n 3 /etc/sysconfig/named ROOTDIR=/var/named/chroot OPTIONS=-4 ENABLE_ZONE_WRITE=yes # rpm -qa|grep bind bind-chroot-9.3.3-9.0.1.el5 bind-9.3.3-9.0.1.el5 bind-libs-9.3.3-9.0.1.el5 bind-utils-9.3.3-9.0.1.el5 what did I do to break it? -- Craig White <craig at tobyhouse.com>