Named failing

We are getting this one again now. Same exact symptom.

I would really like someone from cpanel technical to respond to this one at this juncture. Thanks.

 

Same issue here, fixed after deleting one domain record that was apparently 'out of range' ??? - How can one dns record screw DNS for over 400 zones?

 

cPanel! I hope you read this, I have had exactly the same problem, and have asked other people with cPanel servers and they say the same. It's on the stable build, and it caused downtime for my clients. DNS is now running but it also rebuilt some DNS zones. I've managed to restore some of the complex ones (with many subdomains) from backups.

I have been experiencing some strange DNS messages and issues with the DNS zones rebuilding over the last couple of weeks - just after the automatic cPanel update runs. Perhaps there's a bug that you've missed?

Thanks.

 

One more.. exact same issue on a cPanel box running latest Release versio tree..

ANy news from cPanel?

 

I concur with Infopro, to anyone experiencing this issue - please submit a support ticket so we can properly diagnose this issue and take corrective action: http://tickets.cPanel.net/submit

 

I have just got same email notification as below:

---------------------------------------------------
nameserver failed @ Wed Dec 15 05:17:57 2010. A restart was attempted automagically.
Service Check Method: [check command]

Cmd Service Check Raw Output: Fixed ownership on /etc/named.conf
Fixed ownership on /etc/rndc.key
Fixed ownership on /etc/rndc.conf
---------------------------------------------------

So did anyone find info to diagnose this issue yet?
If yes, please share with us

 

In getting this error last night...

nameserver failed @ Wed Dec 15 01:46:06 2010. A restart was attempted automagically.
Service Check Method: [check command]

Cmd Service Check Raw Output: Fixed ownership on /etc/named.conf
Fixed ownership on /etc/rndc.key
Fixed ownership on /etc/rndc.conf

I checked the yum logs for updates, i'm seeing:

tac /var/log/yum.log |less

Dec 15 00:16:48 Updated: 30:caching-nameserver-9.3.6-4.P1.el5_5.3.x86_64
Dec 15 00:16:48 Updated: 30:bind-devel-9.3.6-4.P1.el5_5.3.i386
Dec 15 00:16:46 Updated: openssl-devel-0.9.8e-12.el5_5.7.x86_64
Dec 15 00:16:44 Updated: 30:bind-devel-9.3.6-4.P1.el5_5.3.x86_64
Dec 15 00:16:40 Updated: openssl-devel-0.9.8e-12.el5_5.7.i386
Dec 15 00:16:38 Updated: 30:bind-utils-9.3.6-4.P1.el5_5.3.x86_64
Dec 15 00:16:37 Updated: 30:bind-9.3.6-4.P1.el5_5.3.x86_64
Dec 15 00:16:36 Updated: 30:bind-libs-9.3.6-4.P1.el5_5.3.i386
Dec 15 00:16:36 Updated: 30:bind-libs-9.3.6-4.P1.el5_5.3.x86_64
Dec 15 00:16:35 Updated: openssl-0.9.8e-12.el5_5.7.x86_64

so, checking for errors;

tac /var/log/messages |grep named |less

getting this;

Dec 15 10:13:49 host named[24058]: max open files (1024) is smaller than max sockets (4096)
Dec 15 10:13:49 host named[24058]: loading configuration from '/etc/named.conf'
Dec 15 10:13:49 host named[24058]: using up to 4096 sockets

(this is in reverse order because i'm using tac as opposed to cat)

resolution may be here;
[CentOS] BIND and latest update (max open files WARNING)

===============================================

After the latest security update for bind (which came out last night), now
there's a new message on syslog, (facility: daemon, severity: warning) every
time you restart named:

max open files (1024) is smaller than max sockets (4096)

After googling for a while the solution seems to be to add this to
/etc/security/limits.conf:

named soft nofile 4096

....and mofity /etc/named.conf in order to add, under the options section:

files 4096;

That seems to work. Of course, you may raise the 4096 but I guess that's
the default in BIND and I was good with that.

I'm not sure why this happend. Maybe before the update bind had a value of
1024 for max.sockets and now it was raised to 4096.

==================================================