If you still have an issue, please, submit a ticket to helpdesk.cloudlinux.com
Overall, restarting named should solve such issue. On some servers I have seen the need to bring up all the IPs, as sometimes they wouldn\'t come up after reboot.
The issues with mail server are not related to CloudLinux. We don\'t touch mail server, control mail server, or alter any of mail server files. Whatever issue you are having is due to server restart, and not due to CloudLinux.
On the other hand -- we have skills to debug and help you resolve mail server issues if you provide the access. Even though it is outside of CloudLinux support, we usually want to make sure that our customers are happy.
We have a partnership with cPanel where they would resolve all CloudLinux related issues, and we have access to their ticketing system for cases where they need help to resolve it.
Please, provide ticket id from tickets.cpanel.net so we can see cPanel\'s support response.
While working on this yesterday, I noticed some things that led me to believe that there MAY be an issue with CloudLinux, but it also looked as though it may have been intentionally removed. However, today I am noticing that the system is reporting that it is using the CloudLinux kernel
At this point, I can stop httpd and try to resolve whatever issue there is with CloudLinux. But I need your confirmation that you want to run CloudLinux.
-bash-3.2# uname -a
Linux server.xxxxx.com 2.6.18-294.26.1.el5.lve0.8.18 #1 SMP Thu Feb 24 12:11:27 EET 2011 x86_64 x86_64 x86_64 GNU/Linux
If we get CloudLinux running properly, we can apply lim its on the accounts and hopefully reduce memory usage. If not, we need to get it properly removed and I can provide information from that perspective.