• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Question /etc/named.conf:9: open: /etc/bind/named.conf.options: file not found

shopuser

Basic Pleskian
Hello,

since yesterday i have this error :

system is :

Ubuntu 20.04.2 LTS,
Plesk Obsidian
Version 18.0.36


Jun 12 11:34:09 server named[67303]: loading configuration from '/etc/named.conf'
Jun 12 11:34:09 server named[67303]: /etc/named.conf:9: open: /etc/bind/named.conf.options: file not found
Jun 12 11:34:09 server named[67303]: loading configuration: file not found
Jun 12 11:34:09 server named[67303]: exiting (due to fatal error)
Jun 12 11:34:09 server systemd[1]: named.service: Main process exited, code=exited, status=1/FAILURE
Jun 12 11:34:09 server systemd[1]: named.service: Failed with result 'exit-code'.
Jun 12 11:34:14 server systemd[1]: named.service: Scheduled restart job, restart counter is at 558.
Jun 12 11:34:19 server systemd[1]: named.service: Scheduled restart job, restart counter is at 559.
Jun 12 11:34:24 server systemd[1]: named.service: Scheduled restart job, restart counter is at 560.
Jun 12 11:34:29 server systemd[1]: named.service: Scheduled restart job, restart counter is at 561.



but the file /etc/bind/named.conf.options exists,

service in plesk DNS-Server (BIND) is Offline cant start

regards
 
hello @shopuser
please check permissions on file /etc/bind/named.conf.options

guess they should be similar as for /etc/named.conf
 
Back
Top