9.1.0 no longer responding to rndc

[Mark_Andrews at isc.org]

> While perusing my zone files for errors, I found some, fixed 'em,  and tried
> to do rndc reload.
> After a pause, I got a message about not being able to reach the network
> (can't remember the message precicely).  After kill  -TERMing named, I did
> rndc reload, to see if I would here "connection refused."  But there was no
> response (I didn't wait long).  I started up named, and it appears to run,
> but the response to rndc reload, after patient waiting, is "rndc: connect:
> timed out"
> 
> What is the named controller attempting to connect to?
> 
> Other network services are happy.  When I dial-up to see if other services
> hosted on that machine work, I find that they do.  So, I'm left scratching
> my head, thankful that somehow, it still (sort of) works.
> 
> Ideas?
> 
> Thank you
> 
> Rick Hagedorn

	BIND 9.1.0 is so old that it is not worth spending time and effort
	on it to see what the cause of this particular bug is.  I recommend
	upgrading to 9.2.0rc10 and if you continue to have problems after
	that please submit a bug report.

	Mark

--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org