Hello,

This should be fixed now. This issue is caused by Cpanel's upcp..Well not an actual issue from Cpanel, instead from CentOS. you can read more once you log into WHM. I am pasting it for the attention of other dedicated customers also. I bolded the significant portion on what you have to do to fix the issue.

===========================
Important Notice Users updating to CentOS 3.5 from CentOS 3.4 may experience a problem with /etc/named.conf reverting to the default state. This is due to a problem with the new caching-nameserver rpm provided with CentOS 3.5. If the problem does occur, it can be easily corrected by running the following command in a root shell:

mv /etc/named.conf /etc/named.conf.CENTOS35UPDATE;mv /etc/named.conf.rpmsave /etc/named.conf;/scripts/restartsrv_named

For more information, please refer to this thread on the cPanel Forums: http://forums.cpanel.net/showthread.php?p=191301#post191301
========================================

Well what happened here is the CentOS update reset/cleared the rndc key, causing the below error, while you try to add a new zone or make any modifications

~~~~~~~~~~~~~~~~
Jun 20 04:12:00 cpanel named[19864]: /etc/named.conf:23: couldn't add command channel 127.0.0.1#953: not found
~~~~~~~~~~~~~~~~~~

/etc/named.conf:23 means error which cause the issue is in line 23 of the file and it refers to rndckey which had to be defined in the conf file and was missing in this case.

I hope this helps.

No you need not.