rndc connect: connection refused

[Bob Vance]

Please note 2 things vis-a-vis BIND 9:

 1) you cannot "start" 'named' version9 via 'rndc' like you could
version8 via 'ndc'.

 2) if 'named' v9 is *not* already running, then *any* 'rndc' command
will return connection refused.

Thus , if you tried

    'rndc start'

you'll get the error that you mentioned.

Note that *any* argument given to 'rndc', when 'named' is not running,
even non-existent commands, such as "xyz", will cause the same error.

I'm not sure exactly why there is not any syntax checking within 'rndc'
*before* an attempt to connect to 'named' is made,
Probably simply to disconnect any coding within 'rndc' from coding
within 'named' so 2 pieces of code don't need to be updated whenever a
new feature is added.
While this is not exactly a bug, I would consider this "an area that
could use further scrutiny" :)


-------------------------------------------------
Tks        | <mailto:BVance at sbm.com>
BV         | <mailto:BobVance at alumni.caltech.edu>
Sr. Technical Consultant,  SBM, A Gates/Arrow Co.
Vox 770-623-3430           11455 Lakefield Dr.
Fax 770-623-3429           Duluth, GA 30097-1511
=================================================





-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Tom Nichols
Sent: Tuesday, April 24, 2001 10:42 AM
To: bind-users
Subject: rndc connect: connection refused


I am upgrading a BSDI 4.2 server to bind 9.1.15c5 and attempting to use
rndc. I copied the sample rndc.conf file to the correct folder but my
guess is there is more to it than just that. Anyone know of a good
reference point for rndc?

(A web search turns up mostly the Region Nine Development Commision)


-- Binary/unsupported file stripped by Listar --
-- Type: text/x-vcard
-- File: tomn.vcf
-- Desc: Card for Tom Nichols