Results 1 to 10 of 10
Thread: connection to remote host closed
-
03-27-2004, 05:16 PM #1Web Hosting Guru
- Join Date
- Mar 2004
- Location
- UK
- Posts
- 277
connection to remote host closed
Dear all,
please forgive the continuing newbie questions.
I am configuring a red hat enterprise server and i keep on getting the following statement while doing something involving bind/named:
"...connection to remote host closed..."
Whichever process I am trying to run or configure seems to continue ok after this statement but i am uncertain why it is coming up repeatedly and what I can do about it - if indeed I need do anything about it.
If I restart bind I get this message:
"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."
Can someone clever enlighten me please.
Many thanksLast edited by jireh; 03-27-2004 at 05:21 PM.
-
03-27-2004, 05:27 PM #2Disabled
- Join Date
- Feb 2003
- Location
- Toronto, Canada
- Posts
- 487
/scripts/fixndc
pico /etc/named.conf
Near the top of that file there are two entries that say rndc-key or rndckey
find the one with a dash and remove the dash so it's all one word then....
service named restart
That'll fix it
-
04-19-2004, 08:03 AM #3WHT Addict
- Join Date
- Aug 2003
- Posts
- 150
I found that this works except you should run /scripts/fixndc twice in a row, and run it after editing named.conf, not before.
Ken O. TKO
-
04-19-2004, 08:55 PM #4Junior Guru Wannabe
- Join Date
- May 2001
- Location
- Coconut Creek, FL.
- Posts
- 31
xAngelx...
Nope that doesn't fix it. here is my output...
Code:Fixndc using rh9/rhes3/fedora support Found key in named.conf .. Found controls in named.conf .. named.conf has already been fixed! root@myserver [/]# service named restart Stopping named: 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.
Just FYI...
any other suggestions?
-
04-29-2004, 01:02 PM #5Newbie
- Join Date
- Apr 2004
- Posts
- 19
Worked for me thanks!
-
04-29-2004, 02:04 PM #6Disabled
- Join Date
- Feb 2003
- Location
- Toronto, Canada
- Posts
- 487
knipper, you didn't do the part about pico /etc/named.conf and remove the dash from rndc-key
You need to do that first, then restart bind (you'll get the error probably once more when you do that but if you restart bind a second time the error will be gone).
-
04-29-2004, 02:21 PM #7Junior Guru Wannabe
- Join Date
- May 2001
- Location
- Coconut Creek, FL.
- Posts
- 31
Thanks for the reply. I searched around, and saw some servers had to have the "-" removed and others had to add it. Since mine did NOT have the dash, I added it, and it fixed the problem.
-
05-06-2004, 05:47 PM #8Newbie
- Join Date
- May 2004
- Posts
- 5
Same problem
I am having the same problem, and i have removed the - from the named.conf
then restarted twice.... i checked the file and the - came back...
so i researched somemore... and removed the - from rndc.conf and named.conf again....
restarted twice... and now i get
root@host [/etc]# /scripts/fixndc
Fixndc using rh9/rhes3/fedora support
Found key in named.conf ..
Found controls in named.conf ..
named.conf has already been fixed!
so no more error from the script, however when I am in WHM, and try to add a record, or edit, or even restart bind...
I still get the connection to remot host closed error... that RNDC error...
Please help... it is so frustrating and my typing is getting worse....
-
05-06-2004, 05:55 PM #9Disabled
- Join Date
- Feb 2003
- Location
- Toronto, Canada
- Posts
- 487
If you are using Fedora you should also pico /etc/sysconfig/named and comment out the 'ROOTDIR=' (put a # in front of it)
Thanks to Peter for figuring that little trick out btw
-
05-06-2004, 06:09 PM #10Newbie
- Join Date
- May 2004
- Posts
- 5
Thank you xAngelx,
I did that and it didnt work, but i decided to reboot, and it seems to work...
Thanks a million
Mike
Next Question would be, is there any way to test to see if my DNS server is working properly? the reason is... I can ping it but when i do a nslookup on it... it will not connect to the dns server...
the server is ns1.carslots.com and ns2.carslots.com... I registered them with the registar already and they have propagated... to ips 65.75.162.50 and .51
Any help would be awsome...
And thanks again for the great advice on the popup thing...
Thanks,
Mike