• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/
  • On Plesk for Linux mod_status is disabled on upgrades to improve Apache security.
    This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.

bind-chroot update for CentOS 3.8 kills named service

B

brooks

Guest
There was an update to bind-chroot last night (8/26/06) that caused the files in /var/named/run-root/var to be moved to /var/named/chroot/var/named/run-root. The update also caused a couple of dirs to be created with incorrect permissions which along with inconsistent config info in /etc/sysconfig/named caused named to fail to start on several of our CentOS 3.8 based servers.

The real problem seems to be that Plesk insists on having the files in /var/named/run-root whereas bind-chroot insists on having the files in /var/named/chroot/. Plesk does what it wants at install time to ensure DNS files are where it expects. Unfortunately an update to bind-chroot moves things around (back) to where it expects to see them (nice).

If you ask me it's a mutual bug, bind-chroot should allow for alternate file locations and Plesk shouldn't need to set up special directories for these files.

I've sent swsoft an email asking for clarification but after looking at the spec file for bind-chroot it's clear that it wants things to be where it expects them, if not it's going to "fix" things.

For now I've fixed things to allow bind-chroot to have its way, but Plesk still uses the old dirs (/var/named/run-root) /so things are still not right.

Sometimes I really hate GUI wrappers (a.k.a. "control panels").
 
Back
Top