Hi,
I seem to be getting some of the errors from above:
Dec 3 21:40:52 localhost named[527]: starting BIND 9.2.3 -c /etc/named.conf
Dec 3 21:40:52 localhost named[527]: using 1 CPU
Dec 3 21:40:52 localhost named[527]: loading configuration from '/etc/named.conf'
Dec 3 21:40:52 localhost named[527]: listening on IPv4 interface lo0, 127.0.0.1#53
Dec 3 21:40:52 localhost named[527]: listening on IPv4 interface en1, 10.0.1.4#53
Dec 3 21:40:52 localhost named[527]: none:0: open: /usr/local/bind9/etc/rndc.key: file not found
Dec 3 21:40:52 localhost named[527]: /etc/named.conf:7: couldn't install keys for command channel 127.0.0.1#54: file not found
Dec 3 21:40:52 localhost named[527]: /etc/named.conf:7: couldn't add command channel 127.0.0.1#54: file not found
Dec 3 21:40:52 localhost named[527]: couldn't open pid file '/usr/local/bind9/var/run/named.pid': No such file or directory
Dec 3 21:40:52 localhost named[527]: exiting (due to early fatal error)
I added the var/run directories under /usr/local/bind9 and it starts up fine, but still no luck with the etc/rndc.key file. Can you explain these problems? Author?
Hi! Thanks for the quick response. I now understand the rndc error. As for the other error:
==========
Dec 3 21:40:52 localhost named[527]: couldn't open pid file '/usr/local/bind9/var/run/named.pid': No such file or directory
Dec 3 21:40:52 localhost named[527]: exiting (due to early fatal error)
===========
Why is it trying to put the pid file under the install directory. I thought the default configuration for the named.pid was in /var/run?
You'll find a post which discusses what rndc does and why you're seeing that error.