BIND update causes DNS Server failure

[sunkoolac]

I am running Plesk 8.3.0 on CentOS 5.0. After Plesk was installed, I updated BIND using CentOS's updater. Now my DNS server will not start. This is the error I get in Plesk:

0: /usr/local/psa/admin/plib/common_func.php3:158
psaerror(string 'Unable to make action: Unable to manage service by dnsmng: dnsmng: Service /etc/init.d/named failed to start')
1: /usr/local/psa/admin/htdocs/server/restart_services.php:28

Has anyone ran into this issue before? Should I even bother updating CentOS after Plesk is installed? Does anyone know how to fix this?

 

[breun]

You should definitely bother updating your OS frequently. Have you checked log files for a reason named might not be starting?

 

[sunkoolac]

The first thing I have found is that "named.conf" can't be located. This is the path where CentOS (and probably Plesk) is trying to find it:
/var/named/chroot//etc (notice the double "/" in the path)

I just did a clean install of CentOS 5.0 then immediately did the OS updates and the DNS service is broken. When I go to the CentOS Service Configuration GUI and select the "named" service, it is turned off for all runlevels and the error message shown is:
"Locating /var/named/chroot//etc/named.conf failed [FAILED]"
(notice the double "/" in the path again)

 

[breun]

On our CentOS 5 machines named.conf is here: /var/named/run-root/etc/named.conf (/etc/named.conf is a symlink to this location).

Do you maybe haven the bind-chroot package installed? It has been known to cause problems with Plesk.

 

[sunkoolac]

Yes, bind-chroot is installed. That was a default package that CentOS installed. If I uninstall it, what else do I have to modify to get the DNS server fixed?

Also, after I did the clean install of CentOS 5.0 the the OS updates (and DNS was broken), I did a clean install of Plesk 8.3.0 and the DNS server problem was fixed and working fine. I do not want to reinstall Plesk if I can avoid it.

 

[breun]

If you did a minimal OS install as prescribed by the Plesk installation instructions then you should not have bind-chroot installed (as Plesk does not install it). I believe you should just be able to remove bind-chroot and restart named.

 

[Highland]

Definitely sounds like bind-chroot is the culprit. I've had a few problems with it myself. Once you've removed it from your machine

yum remove bind-chroot
service named start

add the following line to your yum.conf file under the [main] section

exclude=bind-chroot

 

[breun]

As long as you don't install it yourself again you should be good with the explicit exclude. But it won't hurt either.

 

[sunkoolac]

After uninstalling bind-chroot, DNS still was not working.

I also had to add this line back into /etc/sysconfig/named:
ROOTDIR="/var/named/run-root"
It was removed either by Plesk or uninstalling bind-chroot.

The keys were also different between these two files:
/var/named/run-root/etc/named.conf and
/var/named/run-root/etc/rndc.conf
I just copied and pasted the key from named.conf into rndc.conf then ran
service named start

DNS services are running correctly now. I quadruple checked using Plesk's Services Management, CentOS's BIND Configuration GUI, CentOS's Service Configuration GUI, and the command line by running
service named status.
Stopping, starting, and restarting all work correctly from all four methods.

 

[spaceout]

I'm having the same problem and tried everything above. Still no luck. I'm on RHEL 4.

 

[tiramisu_]

about system upgrade

http://kb.swsoft.com/en/234

 

[sunkoolac]

Tany,
The KB article referenced in your link says to exclude updating the kernel. Why would you want to exclude kernel updates?

 

[breun]

Yeah, I was wondering about that too. Recently there was a local root exploit that affected a wide range of Linux kernels (2.6.17-2.6.24.1), which included current Debian and Red Hat/CentOS kernels: http://it.slashdot.org/article.pl?sid=08/02/10/2011257 Patched kernels were released, but if you exclude kernel* then you won't have gotten the update and users with SSH access can easily get root access to your systems for instance.

 

[SliderMKH6]

This helped me!!! THANK YOU!

I also had to add this line back into /etc/sysconfig/named:
ROOTDIR="/var/named/run-root"
It was removed either by Plesk or uninstalling bind-chroot.