named Failed after capnel update.

[Cash]

Dear all,

I am using cpanel for my sevrer. I just upcp my serverr recently. After that I found named fail and my all webistes cannot up.
I try to use command below to stop and restartnamed, but fail
service named stop
service named restart
error message: rndc: connect failed: 127.0.0.1#953: connection refused

I also try to /scripts/fixndc but it show :
warn [fixrndc] /usr/sbin/rndc status failed: rndc: connect failed: 127.0.0.1#953: connection refused
/scripts/fixrndc failed to fix the rndc key (or named is otherwise broken), please investigate manually

and also fail by use command below
killall -9 named
/etc/init.d/named start
rndc restart

May I know how can I solve it? is it my server firewall block it? How to unblock?

 

[hostmedic]

same here

any update on this - we have the same thing happening here...

 

[h0tmailz]

Just had this happen to me. I got woke up by over 70 text messages to my cell about named failing.

I had to chmod 755 to /etc/rdc.key or w/e the file was.

 

[hostmedic]

after chmod still fail

/scripts/fixrndc failed still fails after chmod.

kills me

 

[cPanelNick]

There was a recent bind rpm update that affected a few people on rhel/centos. We added a workaround/autofix for this in the latest RELEASE build that was published today. You can always run /scripts/rebuilddnsconfig to get things back up if there is a problem with your named.conf.

http://rhn.redhat.com/errata/RHSA-2009-0020.html

 

[JonathanLIVE]

rebuilddnsconfig doesn't work either

I'm in the same boat.. 2 of our 4 DNS servers are now down after attempting the recommended update from Cpanel.

The suggestion to rebuilddns only delivered the following:

-bash-3.2# /scripts/rebuilddnsconfig
Named could not be restarted, any obvious config errors should show up below this line.
No critical problems found, will attempt to regenerate keys regardless.
Creating rndc.conf
Creating /etc/rndc.key
warn [fixrndc] /usr/sbin/rndc status failed: rndc: connect failed: 127.0.0.1#953: connection refused
Restarting named
warn [fixrndc] /usr/sbin/rndc status failed: rndc: connect failed: 127.0.0.1#953: connection refused
/scripts/fixrndc failed to fix the rndc key (or named is otherwise broken), please investigate manually

Pretty useless. Running CentOS 5.2 64bit.

Really need this fixed.

 

[JonathanLIVE]

Oh.. the funniest part is that when you attempt to restart BIND from the WHM interface, it will say that named was restarted OK... even though its not running at all.

Now I can't believe anything the WHM interface claims... I have to double check everything in SSH.

 

[JonathanLIVE]

-bash-3.2# service named start
Starting named: /sbin/service: line 66: 27227 Terminated env -i LANG="$LANG" PATH="$PATH" TERM="$TERM" "${SERVICEDIR}/${SERVICE}" ${OPTIONS}

Thats what I get when I attempt to start named.

 

[chapsrulez]

I'm having the same problem.

Yesterday WHM updated to

cPanel 11.24.4-S33268 - WHM 11.24.2 - X 3.9
CENTOS 4.7 i686 on standard

Named failed, and while trying to restart it via WHM it says named was restarted OK, however when restarting it via SSH i get the following error.

root@gaudi [/]# service named start
Starting named:
Error in named configuration:
/etc/named.conf:39: unknown option 'zone'
/etc/named.conf:44: unknown option 'zone'
/etc/named.conf:49: unknown option 'zone'
/etc/named.conf:54: unknown option 'zone'
/etc/named.conf:59: unknown option 'zone'
/etc/named.conf:64: unknown option 'zone'
/etc/named.conf:69: unknown option 'zone'
/etc/named.conf:74: unknown option 'zone'
/etc/named.conf:79: unknown option 'zone'
/etc/named.conf:84: unknown option 'zone'
/etc/named.conf:89: unknown option 'zone'
/etc/named.conf:94: unknown option 'zone'
/etc/named.conf:99: unknown option 'zone'
/etc/named.conf:104: unknown option 'zone'
/etc/named.conf:109: unknown option 'zone'
/etc/named.conf:114: unknown option 'zone'
/etc/named.conf:119: unknown option 'zone'
/etc/named.conf:124: unknown option 'zone'
/etc/named.conf:129: unknown option 'zone'
/etc/named.conf:134: '}' expected near end of file
[FAILED]

thanks for the help.

 

[cPanelNick]

If you have a problem with your nameserver and can't figure it out please open a ticket.

 

[apolix]

I'm not sure if my problem is related:

I have a main hosting server and one DNS-only server clustered to it. Yesterday I added a second DNS-only server and then upgraded them both to version 11.24.2.

I added the new DNS-only server the the cluster configuration on the hosting server and ran a syncronise all DNS records. The sync ran and reported that it had updated the first DNS-only with no mention of the second one.

I think tried removing and re-adding the access key for the first DNS-only server and now it also does not appear when doing DNS sync's:

Modifying Zone example.com
zone example.com/IN: loaded serial 2007053013
OK
Bind reloading on <hosting> using rndc zone: [example.com]

I have also confirmed the no updates are taking place on the DNS-only servers. They are however online with bind and cpsrvsd running normally.

Where can I find more comprehensive logging the the sync process? Why would the server not be wanting to sync to the other servers in the cluster?

 

[cPanelNick]

I'm not sure if my problem is related:

I have a main hosting server and one DNS-only server clustered to it. Yesterday I added a second DNS-only server and then upgraded them both to version 11.24.2.

I added the new DNS-only server the the cluster configuration on the hosting server and ran a syncronise all DNS records. The sync ran and reported that it had updated the first DNS-only with no mention of the second one.

I think tried removing and re-adding the access key for the first DNS-only server and now it also does not appear when doing DNS sync's:

Modifying Zone example.com
zone example.com/IN: loaded serial 2007053013
OK
Bind reloading on <hosting> using rndc zone: [example.com]

I have also confirmed the no updates are taking place on the DNS-only servers. They are however online with bind and cpsrvsd running normally.

Where can I find more comprehensive logging the the sync process? Why would the server not be wanting to sync to the other servers in the cluster?

Make sure that the server appears in the image in the cluster manager. If it does not make sure you have it set to synchronize and not standalone.

If you still can't get it to work please open a ticket @ https://tickets.cpanel.net/submit/

 

[cisrael]

how cant i fix my named service?

root@nogal [/etc]# /scripts/fixrndc
Named could not be restarted, any obvious config errors should show up below this line.
No critical problems found, will attempt to regenerate keys regardless.
warn [fixrndc] /usr/sbin/rndc status failed: rndc: connect failed: connection refused
Creating rndc.conf
Creating /etc/rndc.key
warn [fixrndc] /usr/sbin/rndc status failed: rndc: connect failed: connection refused
Restarting named
warn [fixrndc] /usr/sbin/rndc status failed: rndc: connect failed: connection refused
/scripts/fixrndc failed to fix the rndc key (or named is otherwise broken), please investigate manually

this problem since cpanel update

 

[cPanelNick]

root@nogal [/etc]# /scripts/fixrndc
Named could not be restarted, any obvious config errors should show up below this line.
No critical problems found, will attempt to regenerate keys regardless.
warn [fixrndc] /usr/sbin/rndc status failed: rndc: connect failed: connection refused
Creating rndc.conf
Creating /etc/rndc.key
warn [fixrndc] /usr/sbin/rndc status failed: rndc: connect failed: connection refused
Restarting named
warn [fixrndc] /usr/sbin/rndc status failed: rndc: connect failed: connection refused
/scripts/fixrndc failed to fix the rndc key (or named is otherwise broken), please investigate manually

this problem since cpanel update

Please open a ticket @ https://tickets.cpanel.net/submit/

 

[skatebored]

named wont start

hello...

1. run /scripts/fixrndc as root, report will tell you [line number] whats wrong with named.conf
2. edit your /etc/named.conf
3. run /scripts/fixrndc again and named will start as usual

enjoi...

 

[JonathanLIVE]

We can open tickets on free dns now?

skate... did you read my last post? Thats exactly what I did.. there was no details reported.

It was only with a lot of manually editing that I tracked down a bad record which for some reason the server allowed to be created. Upon restart it made the server fail.

 

[Nathan D.]

I'm having a similar problem. I am on:

cPanel 11.24.4-C33609 - WHM 11.24.2 - X 3.9
CENTOS 5.2 x86_64 on standard

When my server reboots, there is a problem with DNS and I'm not able to access anything such as WHM or cPanel unless I go to the IP directly (domain.com/whm doesn't work but xxx.xxx.xxx.xxx/whm does). I can easily fix this by stopping and starting named:

service named stop
service named start

What is causing this? How can I fix it? I tried /scripts/fixrndc but it returned nothing. Thanks in advance,

 

[cPanelNick]

I'm having a similar problem. I am on:

cPanel 11.24.4-C33609 - WHM 11.24.2 - X 3.9
CENTOS 5.2 x86_64 on standard

When my server reboots, there is a problem with DNS and I'm not able to access anything such as WHM or cPanel unless I go to the IP directly (domain.com/whm doesn't work but xxx.xxx.xxx.xxx/whm does). I can easily fix this by stopping and starting named:

service named stop
service named start

What is causing this? How can I fix it? I tried /scripts/fixrndc but it returned nothing. Thanks in advance,

Try

/sbin/chkconfig --add named
/sbin/chkconfig --level 2345 named on

 

[Nathan D.]

Try

/sbin/chkconfig --add named
/sbin/chkconfig --level 2345 named on

That worked. So what caused that to need to be done?