ndc / pid file problems?

[Invader Zim]

We have a problem with bind. When we hit the restart link in the services monitor page, or do /usr/local/etc/rc.d/named restart from the freebsd prompt we get the following errors:

Jan 19 19:55:35 servername named[76865]: starting (/etc/namedb/named.conf). named 8.3.7-REL Mon Feb 23 18:30:22 GMT 2004 [email protected]:/usr/obj/usr/src/usr.sbin/named
Jan 19 19:55:35 servername named[76865]: limit files set to fdlimit (1024)
Jan 19 19:55:35 servername named[76865]: unix control "/var/run/ndc" connect failed: Permission denied
Jan 19 19:55:35 servername named[76865]: ctl_server: bind: /var/run/ndc: Address already in use
Jan 19 19:55:35 servername named[76865]: couldn't create pid file '/var/run/named/pid'
Jan 19 19:55:35 servername named[76865]: bind(dfd=20, [our.ip.address].53): Permission denied
Jan 19 19:55:35 servername named[76865]: deleting interface [our.ip.address].53
Jan 19 19:55:35 servername named[76865]: bind(dfd=20, [127.0.0.1].53): Permission denied
Jan 19 19:55:35 servername named[76865]: deleting interface [127.0.0.1].53
Jan 19 19:55:35 servername named[76865]: not listening on any interfaces
Jan 19 19:55:35 servername named[76866]: couldn't create pid file '/var/run/named/pid'
Jan 19 19:55:35 servername named[76866]: Ready to answer queries.

/var/run/named/pid cannot be created for it's already there, but then the file gets deleted. The socket /var/run/ndc is owned by root:wheel and the permissions are srw for owner and all the other ones are off.

Also, named is running twice.

However, when we shut down named, and let directadmin restart it "automagically" named starts up fine.