rndc: connect: unexpected error

[Ian Downard]

If I run rndc after I run named on my linux 2.2.17 box (with hostname
spike.bebop.edu) , I still get an error. Here's the error:

  [root at spike bin]# named -p 53
  [root at spike bin]# rndc -p 53 -s spike.bebop.edu reload 
  rndc: connect: unexpected error

I get the same error if I replace spike.bebop.edu with it's corresponding
ip addr (10.1.1.3).



I realize that I am asking fairly newbie questions here, but to be quite
honest, I have made a considerable effort to find my answers in the bind9
documentation files and this listserves archives - but with little
success.  Too bad /usr/doc/HOWTO/DNS-HOWTO isn't yet up to date with
bind9.  I found that documentation particularly helpful for installing
bind8.

Thanks again for any help.
-Ian


On Wed, 28 Mar 2001, Roy Arends wrote:

> On Tue, 27 Mar 2001, Ian Downard wrote:
> 
> > I'm trying to upgrade my Linux 2.2.17 machine from bind-8.2 to bind-9.1.0,
> > but I can't get rndc to reload.  Here's the command and error:
> >   [shell]# /usr/local/sbin/rndc reload
> >   rndc: connect: connection refused
> > 
> > I've included my named.conf and rndc.conf files below.
> > 
> > (there as a similar thread to this in the archive, but the solution
> > presented there has not worked in my case)
> > 
> > Thanks a bunch for any help,
> > Ian
> 
> Are you sure that named was running at that time ? This message is tipical
> when there's no control channel, thus your OS refuses you to connect to
> the control channel port.
> 
> Regards,
> 
> Roy Arends
> Nominum
> 
> 
>