Named not working since 25-08-2006

[rainboy]

I found that named did stop working for me on my VPS server, didn't know what was going on and started to research the issue.

Found that BIND did have an automatic update done by CPANEL/WHM but also found that Cpanel/WHM apparently did not install the bind-library correctly or not at all.

Here in short the solution for my centOS system, other linux flavours may have other solutions, but for a VPS admin this shouldn't be that much hocus-pocus.

root@ourserver [/etc]# yum update -u bind-libs
Gathering header information file(s) from server(s)
Server: CentOS-3 - Addons
Server: CentOS-3 - Base
Server: CentOS-3 - Extras
Server: CentOS-3 - Updates
Finding updated packages
Downloading needed headers
Cannot find any package matching -u available to be updated.
Resolving dependencies
Dependencies resolved
I will do the following:
[update: bind-libs 20:9.2.4-14_EL3.i386]
Is this ok [y/N]: y
Downloading Packages
Getting bind-libs-9.2.4-14_EL3.i386.rpm
bind-libs-9.2.4-14_EL3.i3 100% |=========================| 548 kB 00:00
Running test transaction:
Test transaction complete, Success!
bind-libs 100 % done 1/2
Completing update for bind-libs - 2/2
Updated: bind-libs 20:9.2.4-14_EL3.i386
Transaction(s) Complete

root@ourserver [/scripts]# ./restartsrv_named
Starting named: [ OK ]

One little note if this isnt working, check your /etc/resolv.conf if it is not using YOUR dns servers or another broken dns server, if you really need a working DNS for downloading the module try opendns.com

More information can be found in the Cpanel forum where they mainly discuss about up2date, which was not installed on my system, and thus not a solution for me.

Hope this will help others with the same problem! Good luck!

Kindest regards,
Patrick

[rainboy]

Quick update, after this fix it appeared that you may want to rebuild your named.conf as mine was empty ! only our own main domain was in there, but not those of our customers.

You may want to use the WHM tool:
/scripts/fixndc

which creates a named.conf.fixndc in the /etc/ directory containing all your customers domains as well. I found that on my system replacing this correct file over my /etc/named.conf was not enough, i also needed to adjust the /var/named/chroot/etc/named.conf before restarting named again.

You can do this with /scripts/restartsrv_named

After this all our domains where reachable again.

Kindest regards,
Patrick

[taotoon]

I faced this problem too.