CentOS - Nov 2009 - rndc start fails with "rndc: connect failed: connection refused"

CentOS 4.8, BIND 9.2.4

Hi All:

I have a rather annoying problem with rndc which I have not been able
to resolve despite much searching and many attempts to correct. When
making changes to our DNS entries I have tried to use the following
procedures:

1. Flush the cache buffers:

   rndc flush

2. Stop named:

   rndc stop

3. Delete the journal files:

   rm *.jnl

4. Edit the forward and/or reverse zone files as necessary.

5. Restart named:

   rndc start

Everything works fine until the last command which fails with:

   rndc: connect failed: connection refused

I can get around this by using "service named start" but I should not
have to do this. Has anyone encountered something similar and can pass
on some words of wisdom?

TIA

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

Hello ,

I am facing same problem but with CentOS 5.4 and BIND 9.3.6 while I
was having 5.3 named was working fine but now it give me same error in
Service configuration panel to start named I have to reboot the system
but if I give Service named restart it stops and fails to start only I
can use service named reload on command line.

I did everything so far but no luck I shall try to go back to CentOS 5.3
thats the option I feel might work for me.

Regards.

On Wed, Nov 25, 2009 at 6:04 PM, Hugh E Cruickshank <hugh at forsoft.com>
wrote:
> CentOS 4.8, BIND 9.2.4
>
> Hi All:
>
> I have a rather annoying problem with rndc which I have not been able
> to resolve despite much searching and many attempts to correct. When
> making changes to our DNS entries I have tried to use the following
> procedures:
>
> 1. Flush the cache buffers:
>
> ? rndc flush
>
> 2. Stop named:
>
> ? rndc stop
>
> 3. Delete the journal files:
>
> ? rm *.jnl
>
> 4. Edit the forward and/or reverse zone files as necessary.
>
> 5. Restart named:
>
> ? rndc start
>
> Everything works fine until the last command which fails with:
>
> ? rndc: connect failed: connection refused
>
> I can get around this by using "service named start" but I should
not
> have to do this. Has anyone encountered something similar and can pass
> on some words of wisdom?
>
> TIA
>
> Regards, Hugh
>
> --
> Hugh E Cruickshank, Forward Software, www.forward-software.com
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos
>


-- 
Best Regards
Tariq Ismail Dalvi
http://www.dalvis.net
tariq at dalvis.net

On Wed, Nov 25, 2009 at 03:04:59PM -0800, Hugh E Cruickshank
wrote:
> CentOS 4.8, BIND 9.2.4
> 
> 1. Flush the cache buffers:
> 
>    rndc flush
> 
> 2. Stop named:
> 
>    rndc stop
> 
> 3. Delete the journal files:
> 
>    rm *.jnl
> 
> 4. Edit the forward and/or reverse zone files as necessary.
> 
> 5. Restart named:
> 
>    rndc start
> 
> Everything works fine until the last command which fails with:
> 
>    rndc: connect failed: connection refused
> 
> I can get around this by using "service named start" but I should
not
> have to do this. Has anyone encountered something similar and can pass
> on some words of wisdom?
	You are going through entirely too many steps.  

	1)  Edit zone file

	2)  rndc reload foo.com

	Also in the steps you have taken above you are stopping bind
	via rndc stop and then trying to start it with the unknown
	"start" command.  Even if "start" was known it would not
work,
	rndc communicated directly with named, and since it was already
	stopped in a previous step there is no way that your "start"
	(or any other command, reload, flush, whatever) could work at
	that point.




							John

-- 
"The Special Olympics is to winners as FOX News is to experts.
If you show up, you are one."

-- Jon Stewart
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://lists.centos.org/pipermail/centos/attachments/20091125/6cd13ac2/attachment-0003.sig>

From: Tariq Ismail Dalvi Sent: November 25, 2009 15:21
> 
> I am facing same problem but with CentOS 5.4 and BIND 9.3.6 while I
> was having 5.3 named was working fine but now it give me same error in
> Service configuration panel to start named I have to reboot the system
> but if I give Service named restart it stops and fails to start only I
> can use service named reload on command line.
Thank you for your reply but your problem seems to be different than
mine. "service named start" and "service named restart" work
fine on
my system it is the "rndc start" which is failing.

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

From: John R. Dennison Sent: November 25, 2009 15:26
> 
> 	You are going through entirely too many steps.  
> 
> 	1)  Edit zone file
> 
> 	2)  rndc reload foo.com
I will give that a try.
> 	Also in the steps you have taken above you are stopping bind
> 	via rndc stop and then trying to start it with the unknown
> 	"start" command.  Even if "start" was known it would
not work,
> 	rndc communicated directly with named, and since it was already
> 	stopped in a previous step there is no way that your "start"
> 	(or any other command, reload, flush, whatever) could work at
> 	that point.
That would explain a lot but it would have been more useful if the
rndc command had returned an error saying something like "start
command unknown" rather than accepting the command and indicating
a communication problem.

Thanks very much for your informative reply.

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

On Thu, Nov 26, 2009 at 1:04 AM, Hugh E Cruickshank <hugh at forsoft.com>
wrote:
> CentOS 4.8, BIND 9.2.4
> 3. Delete the journal files:
> ? rm *.jnl
why to do that?
you can do simple zone update by:
rndc freeze [zone]
if you got error like:
rndc: 'freeze' failed: not found
try than:
rndc freeze [zone] in internal

edit you zone
rndc unfreeze [zone] [in internal]
rndc reload

Hugh E Cruickshank wrote:
> I can get around this by using "service named start" but I should
not
> have to do this. Has anyone encountered something similar and can pass
> on some words of wisdom?
yes, don't use rndc the whole concept is stupid to begin with.

nate

>    rndc: connect failed: connection refused
Here is what works for me:

cd /var/named/chroot/etc
rndc-confgen > rndc.key
chown root.named rndc.key

vi rndc.key and remove everything except the key section.

vi /var/named/chroot/etc/named.conf and 
copy the rndckey from /var/named/chroot/etc/rndc.key
into this section

key "rndckey" {
	algorithm hmac-md5;
	secret "[RNDC key]";
};

I hope this helps,
	Neil

--
Neil Aggarwal, (281)846-8957, http://UnmeteredVPS.net
CentOS 5.4 VPS with unmetered bandwidth only $25/month!
7 day free trial, Google Checkout accepted