From 390a1d85d56296135c2ed4c8e4d7eed62ed519ae Mon Sep 17 00:00:00 2001 From: Mark Andrews Date: Wed, 9 Jun 2004 01:06:26 +0000 Subject: [PATCH] Q: I get "rndc: connect failed: connection refused" when I try to run rndc. --- FAQ | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/FAQ b/FAQ index 966c35f9fd..2bb2a380b5 100644 --- a/FAQ +++ b/FAQ @@ -421,3 +421,29 @@ Q: I get the error message "named: capset failed: Operation not permitted" when starting named. A: The capset module has not been loaded into the kernel. See insmod(8). + + +Q: I get "rndc: connect failed: connection refused" when I try to run + rndc. + +A: This is usually a configuration error. + + First ensure that named is running and no errors are being + reported at startup (/var/log/messages or equivalent). Running + "named -g " from a terminal can help at this + point. + + Secondly ensure that named is configured to use rndc either by + "rndc-confgen -a", rndc-confgen or manually. The Administators + Reference manual has details on how to do this. + + Old versions of rndc-confgen used localhost rather than 127.0.0.1 + in /etc/rndc.conf for the default server. Update /etc/rndc.conf + if necessary so that the default server listed in /etc/rndc.conf + matches the addresses used in named.conf. "localhost" has two + address (127.0.0.1 and ::1). + + If you use "rndc-confgen -a" and named is running with -t or -u + ensure that /etc/rndc.conf has the correct ownership and that + a copy is in the chroot area. You can do this by re-running + "rndc-confgen -a" with appropriate -t and -u arguements.