This has happening for quite a while (dunno whether it has ever worked or not) amd@xxx ~ $ sudo /etc/init.d/named reload * Reloading named.conf and zone files ... [ !! ] although... amd@xxx ~ $ sudo /etc/init.d/named restart * Stopping named ... [ ok ] * Starting named ... [ ok ]
(In reply to comment #0) > This has happening for quite a while (dunno whether it has ever worked or not) > > amd@xxx ~ $ sudo /etc/init.d/named reload > * Reloading named.conf and zone files ... [ !! > ] Works as a charm on multiple different machines here. Is your rndc.key file correct (and referenced correctly in named.conf)? Try: rndc -k `source /etc/conf.d/named && echo $CHROOT/etc/bind/rndc.key` reload If this returns an error, you probably haven't configured the keys or chroot jail correctly.
Ah.. okey, my rndc key was empty... Anyway, without rndc key the reload stuff doesn't look that good... Basically it only does: /etc/init.d/named restart &>/dev/null and then exits, without showing any user-visible messages. [snip] if [ -f $KEY ] ; then ebegin "Reloading named.conf and zone files" rndc -k $KEY reload &>/dev/null eend $? else /etc/init.d/named restart &>/dev/null fi [/snip]
it's just a misconfiguration, thanks for reporting.
