Dear Valued Clients:


cPanel have officially announced that there is an issue while you update from a CentOS 3.5 from CentOS 3.4.
It is making most of the sites unavailable as the old named configuration file is not reverted back after the new instalation.

All the dedicate server owners with cPnel/WHM must be getting an allert in the initila login to the WHM. If you are using any other OS than CentOS, there is absolutely nothing to worry about.

Even the CentOS users need to panic as the fix of the issue has also been mentions in the news alert.

I have found that the same problem can happen if you are using a manual update of the cPanel through /scripts/upcp --force or even with the night cron job .

This may make most of the zones disapear as the update is installing the new bind and saving the old /etc/named.conf to [/b]/etc/named.conf.rpmsave[/b]

It is supposed to revert back the initial named.conf , but it is not.

Here are the steps that can solve the issue for the dedicated server owners.
Login to the shell.
Try to see if the bind is already running or not.
Code:
service named status
If you are getting rndc: connection failure message, do the following steps to fix it. Fire in the following command in the shell.
Code:
/script/updatenow
/scripts/fixnamed
/scritpts/fixndc
/scritpts/fixndc
This will fix the named server and keep it running.

Then to get all your zones back and running do the following.

Code:
#Backup your recent named.conf
mv /etc/named.conf /etc/named.conf.CENTOS35UPDATE

#Replace the old configuration file
mc -f /etc/named.conf.rpmsave /etc/named.conf

#Restart the named 
/scripts/restartsrv_named
This will fix the issue.

If you are not sure or have any doubts after facing the problem, feel free to open a ticket to our Helpdesk, we will be happy to do it for you.

Respectfully,

Mark William