restarting named - rndc: connect failed: operation canceled

[Cowles, Steve]

Noah wrote:
> 
> Hi,
> 
> well #2 appears to be a problem - named is not listeningon port 953
> 
> # netstat -nap | grep 953
> #
> 
> do I need something else in my configuration.  here are the relevant
> /etc/named.conf  lines

Noah,

Sorry, but I'm running out of ideas on why rndc/named are not communicating
at your end. Everything you have done looks correct as far as I can tell.
Could be time for you to check the redhat support site for problems related
to running bind-9.2.3 on RH-8.0.

For reference: I run bind-9.2.3 on FC2 at this end. This is how my version
of bind/named starts up. Note the command channel entry.

# grep named /var/log/messages
Jun 14 09:31:32 excelsior named[1746]: starting BIND 9.2.3 -u named -t
/var/named/chroot
Jun 14 09:31:32 excelsior named[1746]: using 1 CPU
Jun 14 09:31:32 excelsior named[1748]: loading configuration from
'/etc/named.conf'
Jun 14 09:31:32 excelsior named[1748]: no IPv6 interfaces found
Jun 14 09:31:32 excelsior named[1748]: listening on IPv4 interface lo,
127.0.0.1#53
Jun 14 09:31:33 excelsior named[1748]: listening on IPv4 interface eth0,
192.168.8.2#53
Jun 14 09:31:33 excelsior named[1748]: command channel listening on
127.0.0.1#953
[snip] zones loading

Good Luck
Steve Cowles