Hide Forgot
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-24smp alpha; en-US; 0.8) Gecko/20010217 the 'ndc' program doesn't work because named isn't listening on the UNIX socket. Reproducible: Always Steps to Reproduce: 1. service named reload Can also run "/usr/sbin/ndc reload" to see the actual error message. Actual Results: error message Expected Results: named restarted Proper solution is probably 'kill -HUP <named pid>', so that listening on the UNIX socket isn't required. High priority because bindconf depends on this behaviour
The "ndc" program is obsolete and has not been included with bind starting with version 9.0.0, which has been in the tree for months. the init script uses the correct command, /usr/sbin/rndc reload, which works with the current bind package. If it doesn't work, it's a configuration problem (you probably didn't set up rndc keys).
rndc does not work either ("connection refused"). It is unacceptable to require the user to perform bind configuration in order for the user to perform bind configuration! :) The initscripts must function properly without setting up servers, keys, or any other fancy stuff. 'service named reload' must work out of the box. This is the way of the Jedi... I am not Glen, but I personally consider this a MUST-FIX for 7.1, since a package that I have worked on (bindconf) requires this to work correctly in order for configuration changes to take effect.
Preston, I concur with Elliott's assessment -- do you agree this is MUST-FIX?
I'd still say this is NOTABUG: The concept of running *reload* on a service that hasn't been configured (and therefore shouldn't be running) is simply asking for trouble and security problems. service anything reload should never work on a service that isn't running already, and an unconfigured service shouldn't be running. I can switch over to the kill -HUP hack - no problem, but I think this introduces a bug rather than fixing one.
It's changed in 9.1.0-6, but I still think reloading an unconfigured service shouldn't work.
The problem is partly a configuration error too. Try adding the following to /etc/named.conf: controls { inet 127.0.0.1 allow { localhost; }; keys{ "key"; }; }; This actually allows rndc to connect to the named daemon properly.