rndc: connect failed: connection refused

xWho

Well-Known Member
Apr 23, 2003
112
0
166
Why is this happening, please:

Zone slstream.com does not exist, a new zone for alpha.slstream.com will be created.
Bind reloading on alpha using rndc Error reloading bind on alpha: rndc: connect failed: connection refused
Created DNS entry for alpha.slstream.com
Add Complete
???
 

UKDSL

Active Member
Jan 6, 2005
28
0
151
cPanel Access Level
DataCenter Provider
Try running the following:

/scripts/fixnamed
/scripts/fixndc
/scripts/fixndc


If that doesnt work try doing this to your named.conf

Make a backup
cp /etc/named.conf /etc/named.conf-old

Open it up and take this out

controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};

Save it then type:

service named restart

Then run /scripts/fixndc

Also make sure named.conf has the correct permissions
 

xWho

Well-Known Member
Apr 23, 2003
112
0
166
I tried your suggestions and I still get the same error:

rndc: connect failed: connection refused
Whenever trying to add DNS entries, and also when creating new accounts:

Bind reloading on d2295 using rndc
Error reloading bind on d2295: rndc: connect failed: connection refused
 

kalpin

Registered
Jul 13, 2004
2
0
151
has this problem solved ? if not I have same experience and I can solve it manually. If you want I can post it with my way, but I must make sure if this solve or not.
 

cyberwisdom

Well-Known Member
Jun 2, 2003
75
0
156
kalpin said:
has this problem solved ? if not I have same experience and I can solve it manually. If you want I can post it with my way, but I must make sure if this solve or not.
I would like to see it the other way since this fix didn't work for me....
 

djbusyv

Registered
Feb 5, 2005
1
0
151
Might Help

I recieved same error

Error reloading bind on print: rndc: connect failed: connection refused

i was trying to add an spf record -
but it was actually adding the text to the record but not recognizing

My solution: I just clicked - restart DNS/Name Server (BIND)
under restart services

then when i checked to see if it registered changes it did....
 

mydomain

Well-Known Member
Aug 10, 2003
138
0
166
Try this mate:

/scripts/updatenow
/scripts/upcp --force
mv /etc/named.conf /etc/named.old
/scripts/rebuildnamedconf > /etc/named.conf
service named stop
killall -9 named
/scripts/fixndc
/scripts/fixndc

Should fix it. :D
 

x-man

Well-Known Member
Jan 25, 2004
118
0
166
Bad Post!

Sorry, this is bad post, please delete!
 
Last edited:

aspr

Member
Sep 26, 2004
8
0
151
Thanks!

mydomain said:
Try this mate:

/scripts/updatenow
/scripts/upcp --force
mv /etc/named.conf /etc/named.old
/scripts/rebuildnamedconf > /etc/named.conf
service named stop
killall -9 named
/scripts/fixndc
/scripts/fixndc

Should fix it. :D

It worked!
 

Runtime

Member
Jun 28, 2005
13
0
151
This worked great !!! :)
However, the 'bind' is not listed in the Service Manager anymore.
Any ideas how to 'force' list it ?
Thank you.
 

Runtime

Member
Jun 28, 2005
13
0
151
Bijo !!!! THANX !!!!! :)

Those two files did not existed. Two because I requested a memory check for the server,
and when it was done, the server was rebooted and again the same problem with the DNSes appeared. This time the named was gone like the bind from the service list.
However, now they are both there, and I'm waiting to see if the DNSes will start to work properly.
Thank you! :)
 

Runtime

Member
Jun 28, 2005
13
0
151
...... I've fixed the problem. Here's a 'short' summary:

1) Problems with the BIND - I've fixed them using the info in this thread. Thank you!:)

2)No BIND in the service list. Bijo helped - thank you Bijo

3)Memory test, server restart , again problems with the BIND

4)Tried to fix with the info in this thread - didn't work

5)No named no bind in the service list. Bijo's advise helped again:)

6)Tried several times to fix the problem by changing IP addresses, updating DNSes & etc, but nothing helped. Whenever I edit a DNS zone (even if I don't make any changes)
the bind fails to reload. I tried both ways - editing the named.conf , running again all scripts & Cpanel update - no help at all. The IP addresses for both DNSes were correct,
and had the correct entries in /etc/nameserverips file.

7) Feeling helpless and hungry (no time 4 food), I did this (after checking again if everything is as it should be):

mv /etc/named.conf /etc/named.old
/scripts/rebuildnamedconf > /etc/named.conf
service named stop
killall -9 named
/scripts/fixndc
/scripts/fixndc

This (and I don't know why and how) fixed the problem.

The thing that is killing me is why it did not work the previous 4-5 times since my last post...
Being stubborn finally pays-off.....

Thank you for the help!!!! :p

I believe that the problem is in the fact that the server shared IP is xxx.yyy.zzz.254
and I could not use 255 for obvious reason :) Therefor the 2nd ip address (the IP for the 2nd DNS) is .253...
 
Last edited:

mydomain

Well-Known Member
Aug 10, 2003
138
0
166
Runtime said:
...... I've fixed the problem. Here's a 'short' summary:

1) Problems with the BIND - I've fixed them using the info in this thread. Thank you!:)

2)No BIND in the service list. Bijo helped - thank you Bijo

3)Memory test, server restart , again problems with the BIND

4)Tried to fix with the info in this thread - didn't work

5)No named no bind in the service list. Bijo's advise helped again:)

6)Tried several times to fix the problem by changing IP addresses, updating DNSes & etc, but nothing helped. Whenever I edit a DNS zone (even if I don't make any changes)
the bind fails to reload. I tried both ways - editing the named.conf , running again all scripts & Cpanel update - no help at all. The IP addresses for both DNSes were correct,
and had the correct entries in /etc/nameserverips file.

7) Feeling helpless and hungry (no time 4 food), I did this (after checking again if everything is as it should be):

mv /etc/named.conf /etc/named.old
/scripts/rebuildnamedconf > /etc/named.conf
service named stop
killall -9 named
/scripts/fixndc
/scripts/fixndc

This (and I don't know why and how) fixed the problem.

The thing that is killing me is why it did not work the previous 4-5 times since my last post...
Being stubborn finally pays-off.....

Thank you for the help!!!! :p

I believe that the problem is in the fact that the server shared IP is xxx.yyy.zzz.254
and I could not use 255 for obvious reason :) Therefor the 2nd ip address (the IP for the 2nd DNS) is .253...
Great news, glad you found the help on here useful.
 

welo

Well-Known Member
Nov 11, 2002
71
0
156
mydomain said:
Try this mate:

/scripts/updatenow
/scripts/upcp --force
mv /etc/named.conf /etc/named.old
/scripts/rebuildnamedconf > /etc/named.conf
service named stop
killall -9 named
/scripts/fixndc
/scripts/fixndc

Should fix it. :D
Last month my NOC updated my box from FC1 to CentOS 4.3 (not even quite sure how) and ever since then during account creation I was getting the following error:

Error reconfiguring bind on [server]: rndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.

Sometimes restarting BIND/Apache/server worked and sometimes it didn't. The solution posted above seems to have solved it, although while trying to run:

/scripts/updatenow​

...I kept getting:

updatenow should only be run from upcp at /scripts/updatenow line 10.

Uncertain what that was about but everything seems to be working.