Starting on October 19, 2021, we will enable single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
To be prepared for this change and to avoid the need to register during your next ticket submission after the change, we encourage you to create an account here before October 19 using the same email address as your current Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account. You will continue to use ZenDesk authentication until we switch over to single-sign-on on October 19th.

Unable to start bind on Plesk Ubuntu/Debian server: loading configuration from '/etc/named.conf' loading configuration: permission denied

Follow

Comments

4 comments

  • Avatar
    Alexander Garzon

    Where is the Centos  version of this guide?

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Hello Alexander Garzon. CentOS does not have AppArmor, such issues excluded from happening on CentOS. 

    I recommend to take a look to /var/log/messages attempting to start named-chroot service (this is how service name looks like on CentOS).

    0
    Comment actions Permalink
  • Avatar
    Alexander Garzon

    Thank you. I'm aware Centos does  not have Apparmor. My question was more about Centos having the exact same problem (/etc/named.conf: permission denied) but not solution found among Plesk articles.

    Basically Plesk is generating files and zones with permission 0600 instead 0640 and all under root:root instead named:named.

    I have to fix this by forcing chmod 640 in all zones with a cron task

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Hi Alexander Garzon I checked internally, and we did not have such requests as this for CentOS. As well as I verified that by default Plesk should create and use zones with 644 permissions and root:root. 

    I would recommend creating a ticket to support to see what can be wrong.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request