• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Plesk DNSSEC Extension isn't compatible with RedHat 9.1

David Cottle

New Pleskian
Server operating system version
Red Hat Enterprise Linux 9.1 (Plow)
Plesk version and microupdate number
Version 18.0.49 Update #2, last updated on Jan 13, 2023 10:38 AM
I have a paid subscription for Plesk DNSSEC. I just moved hosts and therefore servers and OS. Moved from CentOS-7 (where it works) and then to RedHat-9, where if you add the extension, sign the zone, even restart named-chroot not a problem.

However once you add in the DS records the extension provides (did this multiple times no error in the copy and paste) named-chroot refuses to restart. Also stop, start, anything. If you probe syscontrol its complaining about the errors in the records for the DS entries.

Once again remove the DS enties in the dns zone and it happily restarts.

Its clearly a major bug in the plesk dnssec extension regards bind version in RH9 and possibly other OS based on the version.

Installed Packages
bind.x86_64 32:9.16.23-5.el9_1 @rhel-9-for-x86_64-appstream-rpms
bind-dnssec-doc.noarch 32:9.16.23-5.el9_1 @rhel-9-for-x86_64-appstream-rpms
bind-dnssec-utils.x86_64 32:9.16.23-5.el9_1 @rhel-9-for-x86_64-appstream-rpms
bind-libs.x86_64 32:9.16.23-5.el9_1 @rhel-9-for-x86_64-appstream-rpms
bind-license.noarch 32:9.16.23-5.el9_1 @rhel-9-for-x86_64-appstream-rpms
bind-utils.x86_64 32:9.16.23-5.el9_1 @rhel-9-for-x86_64-appstream-rpms
Available Packages
bind-chroot.x86_64 32:9.16.23-5.el9_1 rhel-9-for-x86_64-appstream-rpms


Cheers,

David
 
If you believe that you have found a bug, please report it here:
 
Hey Peter,

I was actually doing that right after here. Took me longer as the support Plesk page isn’t compatible with Firefox, the login button sent me on a loop back. Used Brave and its okay.

Your request (397131) has been updated. To add additional comments, reply to this email.

So there’s the Plesk support ticket and replied already with the syscontrol messages.

Cheers,

David
 
Back
Top