Error reloading bind on server1: rndc: connect failed: connection refused ?? HELP!

E

E9N_Michio

Member
Jul 11, 2004
12
0
151
hey, for some reason when i add a new account or do something to add ips to DNS i get this error ..

Error reloading bind on server1: rndc: connect failed: connection refused
Click to expand...
Anyone know whats wrong? server1.solid-ice.net resolves to the server defult IP..

Thanks in advanced michio
 
Z

zentity

Well-Known Member
Jun 16, 2004
78
0
156
Hello,

Please try the following within a terminal session

/scripts/fixndc
/etc/init.d/named stop
/etc/init.d/named start

rndc reload

If you still get get an error (connection refused) when reloading named with 'rndc reload'
do

tail -100 /var/log/messages and let us see the output.
 
L

Lestat

Well-Known Member
Sep 13, 2003
199
0
166
Code: 
tail -100 /var/log/messages
Aug 22 16:51:05 home named[14810]: listening on IPv4 interface eth0:6, 64.247.xxx.xxx#53
Aug 22 16:51:05 home named[14810]: listening on IPv4 interface eth0:7, 64.247.18xxx.xxx#53
Aug 22 16:51:05 home named[14810]: couldn't add command channel 127.0.0.1#953: not found
Aug 22 16:51:05 home named[14810]: couldn't add command channel ::1#953: not found
Aug 22 16:51:05 home named[14810]: running
Aug 22 12:51:05 home named: named startup succeeded
Aug 22 12:51:06 home proftpd[14698]: home.pitstopgaming.com (localhost[127.0.0.1]) - FTP no transfer timeout, disconnected
Aug 22 12:51:06 home proftpd[14698]: home.pitstopgaming.com (localhost[127.0.0.1]) - FTP session closed.
Aug 22 12:52:15 home stunnel[3045]: whmhttps connected from 69.142.xxx.xxx:10112
Aug 22 12:52:16 home stunnel[3045]: Connection closed: 1270 bytes sent to SSL, 447 bytes sent to socket
Aug 22 12:52:16 home stunnel[3045]: whmhttps connected from 69.142.xxx.xxx:10113
Aug 22 12:52:20 home stunnel[3045]: Connection closed: 1373 bytes sent to SSL, 1265 bytes sent to socket
Aug 22 12:52:33 home stunnel[3045]: whmhttps connected from 69.142.xxx.xxx:10115
Aug 22 12:52:35 home stunnel[3045]: Connection closed: 1419 bytes sent to SSL, 1009 bytes sent to socket
Aug 22 12:52:35 home stunnel[3045]: whmhttps connected from 69.142.xxx.xxx:10116
Aug 22 12:52:38 home stunnel[3045]: Connection closed: 1373 bytes sent to SSL, 1265 bytes sent to socket
Aug 22 12:52:42 home stunnel[3045]: whmhttps connected from 69.142.174.6:10117
Aug 22 12:54:42 home stunnel[3045]: Connection closed: 149 bytes sent to SSL, 562 bytes sent to socket
Aug 22 12:55:14 home wall[15590]: wall: user root broadcasted 1 lines (34 chars)
Aug 22 12:56:14 home stunnel[16369]: stunnel 4.04 on i686-pc-linux-gnu PTHREAD+LIBWRAP with OpenSSL 0.9.7a Feb 19 2003
Aug 22 12:56:14 home stunnel[16369]: FD_SETSIZE=16384, file ulimit=1024 -> 500 clients allowed
Aug 22 12:56:17 home wall[16392]: wall: user root broadcasted 1 lines (33 chars)
Aug 22 12:56:26 home stunnel[16448]: stunnel 4.04 on i686-pc-linux-gnu PTHREAD+LIBWRAP with OpenSSL 0.9.7a Feb 19 2003
Aug 22 12:56:26 home stunnel[16448]: FD_SETSIZE=16384, file ulimit=1024 -> 500 clients allowed
Aug 22 12:56:42 home stunnel[16449]: whmhttps connected from 69.142.xxx.xxx:10129
Aug 22 12:56:43 home stunnel[16449]: Connection closed: 514 bytes sent to SSL, 396 bytes sent to socket
Aug 22 12:56:43 home stunnel[16449]: whmhttps connected from 69.142.xxx.xxx:10130
Aug 22 12:56:43 home stunnel[16449]: whmhttps connected from 69.142.xxx.xxx:10131
Aug 22 12:56:43 home stunnel[16449]: whmhttps connected from 69.142.xxx.xxx:10132
Aug 22 12:56:44 home stunnel[16449]: Connection closed: 2070 bytes sent to SSL, 652 bytes sent to socket
Aug 22 12:56:44 home stunnel[16449]: whmhttps connected from 69.142.xxx.xxx:10133
Aug 22 12:56:44 home stunnel[16449]: whmhttps connected from 69.142.xxx.xxx:10134
Aug 22 12:56:44 home filelimits: Increasing file system limits succeeded
Aug 22 12:56:44 home stunnel[16449]: Connection closed: 1812 bytes sent to SSL, 643 bytes sent to socket
Aug 22 12:56:44 home stunnel[16449]: whmhttps connected from 69.142.xxx.xxx:10135
Aug 22 12:56:44 home stunnel[16449]: Connection closed: 5321 bytes sent to SSL, 632 bytes sent to socket
Aug 22 12:56:44 home stunnel[16449]: whmhttps connected from 69.142.xxx.xxx:10136
Aug 22 12:56:46 home stunnel[16449]: Connection closed: 5060 bytes sent to SSL, 6702 bytes sent to socket
Aug 22 12:56:50 home stunnel[16449]: Connection closed: 2462 bytes sent to SSL, 4796 bytes sent to socket
Aug 22 12:56:55 home stunnel[16449]: Connection closed: 3161 bytes sent to SSL, 7807 bytes sent to socket
Aug 22 12:58:07 home stunnel[16449]: SSL_read (SSL_ERROR_SYSCALL): Connection reset by peer (104)
Aug 22 12:58:07 home stunnel[16449]: Connection reset: 1192 bytes sent to SSL, 4391 bytes sent to socket
Aug 22 17:01:34 home named[14810]: shutting down
Aug 22 17:01:34 home named[14810]: no longer listening on 127.0.0.1#53
Aug 22 17:01:34 home named[14810]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:01:34 home named[14810]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:01:34 home named[14810]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:01:34 home named[14810]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:01:34 home named[14810]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:01:34 home named[14810]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:01:34 home named[14810]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:01:34 home named[14810]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:01:35 home named[14810]: exiting
Aug 22 13:01:36 home named: named shutdown succeeded
Aug 22 17:01:36 home named[16632]: starting BIND 9.2.3 -u named -t /var/named/chroot
Aug 22 17:01:36 home named[16632]: using 1 CPU
Aug 22 17:01:36 home named[16632]: loading configuration from '/etc/named.conf'
Aug 22 17:01:36 home named[16632]: listening on IPv4 interface lo, 127.0.0.1#53
Aug 22 17:01:36 home named[16632]: listening on IPv4 interface eth0, 64.247.xxx.xxx#53
Aug 22 17:01:36 home named[16632]: listening on IPv4 interface eth0:5, 64.247.xxx.xxx#53
Aug 22 17:01:36 home named[16632]: listening on IPv4 interface eth0:1, 64.247.xxx.xxx#53
Aug 22 17:01:36 home named[16632]: listening on IPv4 interface eth0:2, 64.247.xxx.xxx#53
Aug 22 17:01:36 home named[16632]: listening on IPv4 interface eth0:3, 64.247.xxx.xxx#53
Aug 22 17:01:36 home named[16632]: listening on IPv4 interface eth0:4, 64.247.xxx.xxx#53
Aug 22 17:01:36 home named[16632]: listening on IPv4 interface eth0:6, 64.247.xxx.xxx#53
Aug 22 17:01:36 home named[16632]: listening on IPv4 interface eth0:7, 64.247.xxx.xxx#53
Aug 22 17:01:36 home named[16632]: couldn't add command channel 127.0.0.1#953: not found
Aug 22 17:01:36 home named[16632]: couldn't add command channel ::1#953: not found
Aug 22 17:01:36 home named[16632]: running
Aug 22 13:01:36 home named: named startup succeeded
Aug 22 17:02:12 home named[16632]: shutting down
Aug 22 17:02:12 home named[16632]: no longer listening on 127.0.0.1#53
Aug 22 17:02:12 home named[16632]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:02:12 home named[16632]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:02:12 home named[16632]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:02:12 home named[16632]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:02:12 home named[16632]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:02:12 home named[16632]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:02:12 home named[16632]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:02:12 home named[16632]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:02:12 home named[16632]: exiting
Aug 22 13:02:12 home named: named shutdown succeeded
Aug 22 17:02:23 home named[16687]: starting BIND 9.2.3 -u named -t /var/named/chroot
Aug 22 17:02:23 home named[16687]: using 1 CPU
Aug 22 17:02:23 home named[16687]: loading configuration from '/etc/named.conf'
Aug 22 17:02:23 home named[16687]: listening on IPv4 interface lo, 127.0.0.1#53
Aug 22 17:02:23 home named[16687]: listening on IPv4 interface eth0, 64.247.xxx.xxx#53
Aug 22 17:02:23 home named[16687]: listening on IPv4 interface eth0:5, 64.247.xxx.xxx#53
Aug 22 17:02:23 home named[16687]: listening on IPv4 interface eth0:1, 64.247.xxx.xxx#53
Aug 22 17:02:23 home named[16687]: listening on IPv4 interface eth0:2, 64.247.xxx.xxx#53
Aug 22 17:02:23 home named[16687]: listening on IPv4 interface eth0:3, 64.247.xxx.xxx#53
Aug 22 17:02:23 home named[16687]: listening on IPv4 interface eth0:4, 64.247.xxx.xxx#53
Aug 22 17:02:23 home named[16687]: listening on IPv4 interface eth0:6, 64.247.xxx.xxx#53
Aug 22 17:02:23 home named[16687]: listening on IPv4 interface eth0:7, 64.247.xxx.xxx#53
Aug 22 17:02:23 home named[16687]: couldn't add command channel 127.0.0.1#953: not found
Aug 22 17:02:23 home named[16687]: couldn't add command channel ::1#953: not found
Aug 22 17:02:23 home named[16687]: running
Aug 22 13:02:24 home named: named startup succeeded
Aug 22 13:02:35 home proftpd[16562]: home.domain.com (localhost[127.0.0.1]) - FTP no transfer timeout, disconnected
Aug 22 13:02:35 home proftpd[16562]: home.domain.com (localhost[127.0.0.1]) - FTP session closed.
I have tried the fixes above but still get this error when trying to add my A records for the DNS.
Code: 
Adding an A entry for nameserver ns1.domain.com 
IP=64.247.xxx.xxx Bind reloading on home using rndc zone: [domain.com] Error reloading bind on home: rndc: connect failed: connection refused Add Complete
Anyone have a clue on how to solve this issue? Or is it normal?
 
Last edited:
L

Lestat

Well-Known Member
Sep 13, 2003
199
0
166
Code: 
[email protected] [/etc]# /scripts/fixndc
Fixndc using rh9/rhes3/fedora support
Found controls in named.conf ..
Adding key...
Restarting bind.....Waiting for named to restart..............finished.

named    16884  0.0  1.1 37068 2684 ?        S    13:12   0:00 /usr/sbin/named -u named -t /var/named/chroot

named started ok
Aug 22 17:12:31 home named[16687]: shutting down
Aug 22 17:12:31 home named[16687]: no longer listening on 127.0.0.1#53
Aug 22 17:12:31 home named[16687]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:12:31 home named[16687]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:12:31 home named[16687]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:12:31 home named[16687]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:12:31 home named[16687]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:12:31 home named[16687]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:12:31 home named[16687]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:12:31 home named[16687]: no longer listening on 64.247.xxx.xxx#53
Aug 22 17:12:31 home named[16687]: exiting
Aug 22 13:12:31 home named: named shutdown succeeded
Aug 22 17:12:32 home named[16884]: starting BIND 9.2.3 -u named -t /var/named/chroot
Aug 22 17:12:32 home named[16884]: using 1 CPU
Aug 22 17:12:32 home named[16884]: loading configuration from '/etc/named.conf'
Aug 22 17:12:32 home named[16884]: listening on IPv4 interface lo, 127.0.0.1#53
Aug 22 17:12:32 home named[16884]: listening on IPv4 interface eth0, 64.247.xxx.xxx#53
Aug 22 17:12:32 home named[16884]: listening on IPv4 interface eth0:5, 64.247.xxx.xxx#53
Aug 22 17:12:32 home named[16884]: listening on IPv4 interface eth0:1, 64.247.xxx.xxx#53
Aug 22 17:12:32 home named[16884]: listening on IPv4 interface eth0:2, 64.247.xxx.xxx#53
Aug 22 17:12:32 home named[16884]: listening on IPv4 interface eth0:3, 64.247.xxx.xxx#53
Aug 22 17:12:32 home named[16884]: listening on IPv4 interface eth0:4, 64.247.xxx.xxx#53
Aug 22 17:12:32 home named[16884]: listening on IPv4 interface eth0:6, 64.247.xxx.xxx#53
Aug 22 17:12:32 home named[16884]: listening on IPv4 interface eth0:7, 64.247.xxx.xxx#53
Aug 22 17:12:32 home named[16884]: couldn't add command channel 127.0.0.1#953: not found
Aug 22 17:12:32 home named[16884]: couldn't add command channel ::1#953: not found
Aug 22 17:12:32 home named[16884]: running
Aug 22 13:12:32 home named: named startup succeeded
Done
All fixed
[email protected] [/etc]# /etc/init.d/named stop
Stopping named: rndc: connect failed: connection refused
                                                           [  OK  ]
[email protected] [/etc]# /etc/init.d/named start
Starting named:                                            [  OK  ]
[email protected] [/etc]# rndc reload
rndc: connect failed: connection refused
[email protected] [/etc]#
 
S

sawbuck

Well-Known Member
Jan 18, 2004
1,365
10
168
cPanel Access Level
Root Administrator
Anyone have a clue on how to solve this issue? Or is it normal?
Click to expand...
No not normal. Your zone files won't be updated until this issue is fixed. Assume you have searched this forum and tried the available fixes? Looks like you are running RH9?
 
L

Lestat

Well-Known Member
Sep 13, 2003
199
0
166
I have ran multiple fixes through out this forum. I am running fedora core 2. Nothing has seemed to help.
 
L

Lestat

Well-Known Member
Sep 13, 2003
199
0
166
Thanks found a little note on there.... this is what fixed it...


If you are using Fedora you should also nano /etc/sysconfig/named and comment out the 'ROOTDIR=' (put a # in front of it)
Click to expand...
All is better now...
 
P

PowWeb

Active Member
Oct 22, 2004
26
0
151
I have the same problem. here is my output.

[email protected] [~]# tail -100 /var/log/messages
Oct 22 15:21:58 wh2 named[966]: no longer listening on 70.X.X.X#53
Oct 22 15:21:58 wh2 named[966]: no longer listening on 70.X.X.X#53
Oct 22 15:21:58 wh2 named[966]: no longer listening on 70.X.X.X#53
Oct 22 15:21:58 wh2 named[966]: no longer listening on 70.X.X.X#53
Oct 22 15:21:58 wh2 named[966]: no longer listening on 70.X.X.X#53
Oct 22 15:21:58 wh2 named[966]: exiting
Oct 22 15:21:59 wh2 named: named shutdown succeeded
Oct 22 15:22:01 wh2 named[31707]: starting BIND 9.2.4rc6 -u named
Oct 22 15:22:01 wh2 named[31707]: using 1 CPU
Oct 22 15:22:01 wh2 named: named startup succeeded
Oct 22 15:22:01 wh2 named[31707]: loading configuration from '/etc/named.conf'
Oct 22 15:22:01 wh2 named[31707]: no IPv6 interfaces found
Oct 22 15:22:01 wh2 named[31707]: listening on IPv4 interface lo, 127.0.0.1#53
Oct 22 15:22:01 wh2 named[31707]: listening on IPv4 interface eth0, 70.X.X.X#53
Oct 22 15:22:01 wh2 named[31707]: listening on IPv4 interface eth0:1, 70.X.X.X#53
Oct 22 15:22:01 wh2 named[31707]: listening on IPv4 interface eth0:2, 70.X.X.X#53
Oct 22 15:22:01 wh2 named[31707]: listening on IPv4 interface eth0:3, 70.X.X.X#53
Oct 22 15:22:01 wh2 named[31707]: listening on IPv4 interface eth0:4, 70.X.X.X#53
Oct 22 15:22:01 wh2 named[31707]: listening on IPv4 interface eth0:5, 70.X.X.X#53
Oct 22 15:22:01 wh2 named[31707]: listening on IPv4 interface eth0:6, 70.X.X.X#53
Oct 22 15:22:01 wh2 named[31707]: listening on IPv4 interface eth0:7, 70.X.X.X#53
Oct 22 15:22:01 wh2 named[31707]: listening on IPv4 interface eth0:8, 70.X.X.X#53
Oct 22 15:22:01 wh2 named[31707]: listening on IPv4 interface eth0:9, 70.X.X.X#53
Oct 22 15:22:01 wh2 named[31707]: listening on IPv4 interface eth0:10, 70.X.X.X#53
Oct 22 15:22:02 wh2 named[31707]: listening on IPv4 interface eth0:11, 70.X.X.x#53
Oct 22 15:22:02 wh2 named[31707]: listening on IPv4 interface eth0:12, 70.X.X.X#53
Oct 22 15:22:02 wh2 named[31707]: command channel listening on 127.0.0.1#953
Oct 22 15:22:02 wh2 named[31707]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Oct 22 15:22:02 wh2 named[31707]: zone domain1.com/IN: loaded serial 2004101301
Oct 22 15:22:02 wh2 named[31707]: zone domain2.com/IN: loaded serial 2004101301
Oct 22 15:22:03 wh2 named[31707]: zone domain3.com/IN: loaded serial 2004101310
Oct 22 15:22:03 wh2 named[31707]: dns_rdata_fromtext: /var/named/wh2.tcpip-inc.com.db:4: near 'root.tcpipinc..servermatrix.com.': empty label
Oct 22 15:22:03 wh2 named[31707]: zone wh2.tcpip-inc.com/IN: loading master file /var/named/wh2.tcpip-inc.com.db: empty label
Oct 22 15:22:03 wh2 named[31707]: zone fantadm.localdomain/IN: loaded serial 2004101901
Oct 22 15:22:03 wh2 named[31707]: zone localhost/IN: loaded serial 42
Oct 22 15:22:04 wh2 named[31707]: zone zoohost.net/IN: loaded serial 2004101501
Oct 22 15:22:04 wh2 named[31707]: running
Oct 22 15:22:04 wh2 named[31707]: zone domain1.com/IN: sending notifies (serial 2004101301)
Oct 22 15:22:04 wh2 named[31707]: zone domain2.com/IN: sending notifies (serial 2004101301)
Oct 22 15:22:04 wh2 named[31707]: zone domain4.net/IN: sending notifies (serial 2004101501)
Oct 22 15:22:04 wh2 named[31707]: zone domain3.com/IN: sending notifies (serial 2004101310)
Oct 22 15:22:04 wh2 named[31707]: zone fantadm.localdomain/IN: sending notifies (serial 2004101901)
Oct 22 15:22:23 wh2 named[31707]: shutting down: flushing changes
Oct 22 15:22:23 wh2 named[31707]: stopping command channel on 127.0.0.1#953
Oct 22 15:22:23 wh2 named[31707]: no longer listening on 127.0.0.1#53
Oct 22 15:22:23 wh2 named[31707]: no longer listening on 70.X.X.X#53
Oct 22 15:22:23 wh2 named[31707]: no longer listening on 70.X.X.x#53
Oct 22 15:22:23 wh2 named[31707]: no longer listening on 70.X.X.X#53
Oct 22 15:22:23 wh2 named[31707]: no longer listening on 70.X.X.X#53
Oct 22 15:22:23 wh2 named[31707]: no longer listening on 70.X.X.X#53
Oct 22 15:22:23 wh2 named[31707]: no longer listening on 70.X.X.X#53
Oct 22 15:22:23 wh2 named[31707]: no longer listening on 70.X.X.X#53
Oct 22 15:22:23 wh2 named[31707]: no longer listening on 70.X.X.X#53
Oct 22 15:22:23 wh2 named[31707]: no longer listening on 70.X.X.X#53
Oct 22 15:22:23 wh2 named[31707]: no longer listening on 70.X.X.X#53
Oct 22 15:22:23 wh2 named: succeeded
Oct 22 15:22:24 wh2 named[31707]: no longer listening on 70.X.X.X#53
Oct 22 15:22:24 wh2 named[31707]: no longer listening on 70.X.X.X#53
Oct 22 15:22:24 wh2 named[31707]: no longer listening on 70.X.X.X#53
Oct 22 15:22:24 wh2 named[31707]: exiting
Oct 22 15:22:34 wh2 named[31754]: starting BIND 9.2.4rc6 -u named
Oct 22 15:22:34 wh2 named[31754]: using 1 CPU
Oct 22 15:22:34 wh2 named: named startup succeeded
Oct 22 15:22:35 wh2 named[31754]: loading configuration from '/etc/named.conf'
Oct 22 15:22:35 wh2 named[31754]: no IPv6 interfaces found
Oct 22 15:22:35 wh2 named[31754]: listening on IPv4 interface lo, 127.0.0.1#53
Oct 22 15:22:35 wh2 named[31754]: listening on IPv4 interface eth0, 70.X.X.X#53
Oct 22 15:22:35 wh2 named[31754]: listening on IPv4 interface eth0:1, 70.X.X.X#53
Oct 22 15:22:35 wh2 named[31754]: listening on IPv4 interface eth0:2, 70.X.X.X#53
Oct 22 15:22:35 wh2 named[31754]: listening on IPv4 interface eth0:3, 70.X.X.X#53
Oct 22 15:22:35 wh2 named[31754]: listening on IPv4 interface eth0:4, 70.X.X.X#53
Oct 22 15:22:35 wh2 named[31754]: listening on IPv4 interface eth0:5, 70.X.X.X#53
Oct 22 15:22:35 wh2 named[31754]: listening on IPv4 interface eth0:6, 70.X.X.X#53
Oct 22 15:22:35 wh2 named[31754]: listening on IPv4 interface eth0:7, 70.X.X.X#53
Oct 22 15:22:35 wh2 named[31754]: listening on IPv4 interface eth0:8, 70.X.X.X#53
Oct 22 15:22:35 wh2 named[31754]: listening on IPv4 interface eth0:9, 70.X.X.X#53
Oct 22 15:22:35 wh2 named[31754]: listening on IPv4 interface eth0:10, 70.X.X.X#53
Oct 22 15:22:35 wh2 named[31754]: listening on IPv4 interface eth0:11, 70.X.X.X#53
Oct 22 15:22:35 wh2 named[31754]: listening on IPv4 interface eth0:12, 70.X.X.X#53
Oct 22 15:22:35 wh2 named[31754]: command channel listening on 127.0.0.1#953
Oct 22 15:22:36 wh2 named[31754]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Oct 22 15:22:36 wh2 named[31754]: zone domain1.com/IN: loaded serial 2004101301
Oct 22 15:22:36 wh2 named[31754]: zone domain2.com/IN: loaded serial 2004101301
Oct 22 15:22:36 wh2 named[31754]: zone domain3.com/IN: loaded serial 2004101310
Oct 22 15:22:36 wh2 named[31754]: dns_rdata_fromtext: /var/named/wh2.tcpip-inc.com.db:4: near 'root.tcpipinc..servermatrix.com.': empty label
Oct 22 15:22:37 wh2 named[31754]: zone wh2.tcpip-inc.com/IN: loading master file /var/named/wh2.tcpip-inc.com.db: empty label
Oct 22 15:22:37 wh2 named[31754]: zone fantadm.localdomain/IN: loaded serial 2004101901
Oct 22 15:22:37 wh2 named[31754]: zone localhost/IN: loaded serial 42
Oct 22 15:22:37 wh2 named[31754]: zone zoohost.net/IN: loaded serial 2004101501
Oct 22 15:22:37 wh2 named[31754]: running
Oct 22 15:22:37 wh2 named[31754]: zone domain1.com/IN: sending notifies (serial 2004101301)
Oct 22 15:22:37 wh2 named[31754]: zone domain2.com/IN: sending notifies (serial 2004101301)
Oct 22 15:22:38 wh2 named[31754]: zone domain4.net/IN: sending notifies (serial 2004101501)
Oct 22 15:22:38 wh2 named[31754]: zone domain3.com/IN: sending notifies (serial 2004101310)
Oct 22 15:22:38 wh2 named[31754]: zone fantadm.localdomain/IN: sending notifies (serial 2004101901)
Oct 22 15:22:41 wh2 named[31754]: loading configuration from '/etc/named.conf'
Oct 22 15:22:41 wh2 named[31754]: no IPv6 interfaces found
Oct 22 15:22:41 wh2 named[31754]: dns_rdata_fromtext: /var/named/wh2.tcpip-inc.com.db:4: near 'root.tcpipinc..servermatrix.com.': empty label
Oct 22 15:22:41 wh2 named[31754]: zone wh2.tcpip-inc.com/IN: loading master file /var/named/wh2.tcpip-inc.com.db: empty label
Oct 22 15:23:02 wh2 named[31754]: received notify for zone 'tcpip-inc.com': not authoritative


Not sure but do you think it could have something to do with the following??? near 'root.tcpipinc..servermatrix.com.': empty label
That was the name that the server company gave the box. I have had them change the name of the box to wh2.tcpip-inc.com but I see that it still shows up here as root.tcpipinc..servermatrix.com
 
P

PowWeb

Active Member
Oct 22, 2004
26
0
151
Sorry

Code: 
# Do not remove the following line, or various programs
# that require network functionality will fail.
70.84.251.178		wh2.tcpip-inc.com wh2 tcpipinc 
127.0.0.1		localhost
 
O

oSM

Well-Known Member
Aug 18, 2001
47
0
306
I'm going to paste the contents of the above fix here just in case that site goes down in the future or something happens. Its so useful. :)

Thanks to hostinglife.com and whoever contributed the below!

-------
RNDC Error Fix
Some installations of WHM/CPanel come with a RNDC error. This error is somewhat common now, and is easily fixed by a couple of methods. Before your name servers work you need to fix the NDC Error. The RNDC Error is nothing major, and should not take more than 15 minutes (if that) to fix. Please read below to fix the RNDC Error.

Simple Fix

Login to your server through SSH
Type:
cd /scripts
Type:
./updatenow
Type:
./fixndc
The above error will fix certain aspects of the RNDC Error, and sometimes fix all the problems. However during certain installations the problem will still exist, this is where RND Error Fix #2 comes in.

RNDC Error Fix #2

Login to your server through SSH.
Type:
pico /etc/rndc.conf
Search for "rndc-key" and replace it with "rndckey"
CTRL-W is how to search in PICO.
CTRL-X Y to save and exit
Type:
pico /etc/named.conf
Search for "rndc-key" and replace it with "rndckey"
CTRL-W is how to search in PICO.
CTRL-X Y to save and exit
After that type:
/scripts/fixnamed
After that type:
/scripts/fixndc
If step #5 still produced an error type:
/scripts/fixndc
There should be no error now.
Now we will restart named (BIND)
Type: service named restart
If you get an error simply restart again.
Type: service named restart
Now you should get no error...
 
You must log in or register to reply here.
Thread starter Similar threads Forum Replies Date
craigedmonds Error reloading bind on ns2: rndc: 'reload' failed: failure Domain Management 3
B Error from domain wrapper: Bind reloading on server using rndc zone Domain Management 1
J Error reloading bind? What would cause this? Domain Management 4
G Error reloading bind Domain Management 3
nickb HELP Error reloading bind on *hostnamehere*: rndc: get config key list: not found Domain Management 9
Similar threads
Error reloading bind on ns2: rndc: 'reload' failed: failure
Error from domain wrapper: Bind reloading on server using rndc zone
Error reloading bind? What would cause this?
Error reloading bind
HELP Error reloading bind on *hostnamehere*: rndc: get config key list: not found
Top Bottom