• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

DNS Server (BIND) turned itself off?

A

Antidote

Guest
This morning I woke up to find all my websites down. After further inspection in the Plesk 8.3 cp I found that "DNS Server (BIND)" had turned itself off.

Why would it do this and how can I stop this happening again?
 
I have just experianced the same problem. Did you find the Antidote...er... Antidote?
 
To enable service

Code:
chkconfig named on


To see why it failed (stoped)
Code:
grep -i named /var/log/messages

That will give you a heads up on why the service failed - as to never having it happen again, I think that is never going to happen - no matter what you do its always possible for something to happen due to a stupid user, configuration error, etc.

But at least this will point you in the right direction for troubleshooting.
 
Back
Top