• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • 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.

Bind Stops Responding

S

spage911

Guest
Hi,

My server did an update on friday that installed the caching-nameserver rpm. I have removed it, restored the named.conf, created the sym links to named.conf and rndc.key that are located in /var/named/run-root/etc verified that all keys match and re-started bind. Everything will work fine for a few hours but then names are no longer resolved. Named shows as still running when I do a ps aux and does not respond to service named stop so I kill the process and restart named and everything is fine for awhile until the same thing happens. I also upgraded to plesk 8.4 from 8.3

Anyone have any ideas why it locks up?

Jul 28 14:45:02 srv1 clamd[14694]: SelfCheck: Database status OK.
Jul 28 14:53:41 srv1 named[17406]: starting BIND 9.2.4 -u named -c /etc/named.conf -u named -t /var/named/run-root
Jul 28 14:53:41 srv1 named[17406]: using 2 CPUs
Jul 28 14:53:41 srv1 named[17406]: loading configuration from '/etc/named.conf'
Jul 28 14:53:41 srv1 named[17406]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 28 14:53:41 srv1 named[17406]: listening on IPv4 interface eth0, XX.XX.XX.XX#53
Jul 28 14:53:41 srv1 named[17406]: listening on IPv4 interface eth0:0, XX.XX.XX.XX#53
Jul 28 14:53:41 srv1 named[17406]: command channel listening on 127.0.0.1#953
Jul 28 14:53:41 srv1 named[17406]: zone XXX.net/IN: sending notifies (serial 1217026029)
Jul 28 14:53:41 srv1 named: named startup succeeded
Jul 28 14:53:41 srv1 named[17406]: zone XXX.com/IN: sending notifies (serial 1217026031)
Jul 28 14:53:41 srv1 named[17406]: running

There are no errors in messages log that I can find


Thanks
Scott
 
Remove the caching only server and restart bind. Should work fine.

--Prowler318.

Also you might want to think about updating BIND or securing ....
 
Back
Top