Articles in this section

See more

Unable to start named/bind DNS in Plesk: unknown option 'version'

Avatar
Renan Poss Moreira
Updated
kb: technical Plesk Obsidian for Linux

Applicable to:

  • Plesk Obsidian for Linux

Symptoms

  • It is not possible to start bind/named service, the following error is shown:

    # systemctl status named-chroot
    Mar 21 05:48:19 named-checkconf: /etc/named-user-options.conf:1: unknown option 'version'
    Mar 21 05:48:19 named-checkconf: /etc/named-user-options.conf:2: unknown option 'auth-nxdomain'
    Mar 21 05:48:19 systemd: named-chroot.service: control process exited, code=exited status=1

Cause

Custom directive include "/etc/named-user-options.conf" specified in /etc/named.conf

Resolution

  1. Login to the server via SSH.
  2. Check that include "/etc/named-user-options.conf" is included only in the top of /etc/named.conf, This directive must exist only once within the file:

    CONFIG_TEXT: options {
    include "/etc/named-user-options.conf";
    allow-recursion {
    localnets;
    };

  3. Remove any extra include "/etc/named-user-options.conf" directives, save and close the file.
  4. Restart the bind/named service:

# systemctl restart named-chroot

Comments

1 comment

Sort by Date Votes
  • Avatar
    Ehud Ziegelman (Edited )

    Can you please explain why was this include in place, and what should have been in it?

    Also after removing it, I could not start the service:

    # systemctl status named-chroot
    Unit named-chroot.service could not be found.

     

    Could the issue of the srvice not found, be related to the usage of route53 AWS extension?

    0

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles