
Troubleshooting BIND
|
67
Because named does not have this new key, we must now kill the named process and
restart it. For this we make use of the system command killall, which takes the full
pathname of the named program. To stop named as gracefully as possible, we do two
killall commands with a few seconds pause in between, then restart named:
server1:~# killall -TERM /usr/sbin/named
server1:~# killall -KILL /usr/sbin/named
/usr/sbin/named: no process killed
server1:~# /etc/init.d/bind9 start
Starting domain name service: named.
server1:~# rndc status
number of zones: 6
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
server is up and running
server1:~#
named Starts but Does Not Resolve Names
Now, let’s look at situations where named isn’t running properly. Incorrectly located
BIND files often cause problems, especially in chroot environments where the BIND
files are placed in an isolated directory.
If named starts OK but does not load any zone files, they may not be present in the
isolated directory. You’ll need to look at the /var/log/syslog file to see if that’s the
case. Here’s an example from the log:
starting BIND 9.2.4 -u bind -t /var/lib/named
using 1 CPU
loading configuration from '/etc/bind/named.conf'
listening on IPv4 interface lo, 127.0.0.1#53
listening on IPv4 interface eth0, 70.253.158.42#53
command channel listening on 127.0.0.1#953
command channel ...