• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

bind stops after 1 minute start

ValdisS

New Pleskian
Does anyone had problem with bind?
bind stops after 1 minute start.
syslog does not show any errors.

VPS have free 4GB ram.
Tried to restart server. Nothing changed.

Any ideas?
 
In /var/log/messages there are lot of
rsyslogd-2177: imuxsock begins to drop messages from pid xxxxx due to rate-limiting
rsyslogd-2177: imuxsock lost xxx messages from pid xxxxx due to rate-limiting

and nothing about bind/named.


But now I can tell that bind is restarted by vps hoster:
"The process named is potential ddos risk. 100% CPU Time ddos Bug with dns cache and libdns on some versions".


Anyway, thank you. (-:
 
Check /var/log/messages on hardware node but not on VPS. Maybe there are kernel OOM killers which kills named processes in VPS due to lack of resources.
 
Back
Top