Linux Quick Fix Notebook by Peter Harrison

Author:Peter Harrison
Language: eng
Format: mobi
Publisher: UNKNOWN
Published: 2018-06-16T23:00:00+00:00

TROUBLESHOOTING BIND

One of the most common culprits of BIND problems is incorrectly located chroot files. If you have the BIND chroot package installed, make sure the configuration files are located in the chroot directory.

Here’s a quick list of symptoms that indicate your files may not be located correctly.

☞ The named daemon starts without loading any zone files. Here is a sample of the /var/log/messages file that shows that named doesn’t load them:.

Nov 9 17:35:41 bigboy named[1157]: starting BIND 9.2.3 -u named -t /var/named/chroot

Nov 9 17:35:41 bigboy named[1157]: using 1 CPU

Nov 9 17:35:41 bigboy named[1157]: loading configuration from ‘/etc/named.conf’

Nov 9 17:35:41 bigboy named[1157]: listening on IPv4 interface lo, 127.0.0.1#53

Nov 9 17:35:41 bigboy named[1157]: listening on IPv4 interface eth0, 10.41.32.71#53

Nov 9 17:35:41 bigboy named[1157]: command channel listening on 127.0.0.1#953

Nov 9 17:35:41 bigboy named[1157]: command channel listening on ::1#953

Nov 9 17:35:41 bigboy named[1157]: running

☞ Restarting named gives rndc “connect failed” messages:

[root@bigboy tmp]# service named restart

Stopping named: rndc: connect failed: connection refused [ OK ]

Starting named: [ OK ]

[root@bigboy tmp]#

☞ The chroot files are empty:

[root@bigboy tmp]# cat /var/named/chroot/etc/named.conf

[root@bigboy tmp]# cat /var/named/chroot/etc/rndc.key

[root@bigboy tmp]#

To correctly relocate the files:

1. Copy the /etc/rndc.* and /etc/named.conf files to the /var/named/chroot/etc/ directory:

[root@bigboy tmp]# cp -f /etc/rndc.* /var/named/chroot/etc/ [root@bigboy tmp]# cp /etc/named.conf /var/named/chroot/etc/

2. Restart named twice; it should shutdown correctly without error the second time.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.