• 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.

Can I update the bind package from the CentOS repo?

GiorgosP

New Pleskian
This is my first post to the parallels forum, so please be patient with me :)

I am running Plesk 8.6.0 on a CentOS release 5.2 (Final).

The problem is that named (bind) has this strange behavior: It restarts at some intervals (this is OK), but sometimes does not start again, without leaving any error messages:

...
...
messages:Feb 3 17:33:38 xxx named[5793]: zone xxxx.gr/IN: loaded serial 2009112001
messages:Feb 3 17:33:38 xxx named[5793]: zone xxxgr/IN: loaded serial 2010012102
messages:Feb 3 17:33:38 xxx named[5793]: zone xxxxgr/IN: loaded serial 2009060501
messages:Feb 3 17:33:38 xxx named[5793]: running
messages:Feb 3 17:33:47 xxx named[5793]: shutting down: flushing changes
messages:Feb 3 17:33:47 xxx named[5793]: stopping command channel on 127.0.0.1#953
messages:Feb 3 17:33:47 xxx named[5793]: no longer listening on 127.0.0.1#53
messages:Feb 3 17:33:47 xxx named[5793]: no longer listening on xxxx#53
messages:Feb 3 17:33:47 xxx named[5793]: exiting

Normally, after reloading the zones, it should restart. Afterwards, when I saw that it is down, I just started it from the panel and all was working again.

Bind version is
Version : 9.3.4
Release : 6.0.2.P1.el5_2
Repo : installed

and the CentOS repo has:

Available Packages
Version : 9.3.6
Release : 4.P1.el5_4.2
Repo : updates


So I have two questions: If I upgrade my bind, will I have problem with the Plesk version I'm running?
And the same question in general: The versions of plesk require specific package versions? Because I'm seeing many updates from yum that I fear upgrading in order not to break Plesk...

Thanks!
Giorgos
 
Back
Top