• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Forwarded to devs DNSSEC not included in backup/restore

DigitS

New Pleskian
TITLE:
DNSSEC not included in backup/restore
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Westmere E56xx/L56xx/X56xx (Nehalem-C) (4 core(s))
8GB Memory
300GB SSD
CentOS Linux 7.4.1708 (Core)
Plesk Onyx v17.5.3_build1705170317.16 os_CentOS 7
PROBLEM DESCRIPTION:
Previously posted as feature request, but redirected here:

Recently I had to restore a server with a couple of domains with DNSSEC, and found that DNSSEC had been disabled during the restore.

This basically means that dns was not working (because the restored domains had no signatures) until the DNSSEC had been re-enabled and the new keys had been copied to the registrar.

It seems that DNSSEC data is not included in the Plesk backup/restore.​
STEPS TO REPRODUCE:
1. Create a full backup using Plesk backup/restore signed with password.
2. Install a new server with Plesk.
3. Do a full system restore (including system settings, keys, etc.)​
ACTUAL RESULT:
Plesk is restored with DNSSEC disabled on all domains.​
EXPECTED RESULT:
Plesk is restored with DNSSEC enabled on domains that had DNSSEC enabled during the backup.​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
Developers have confirmed this issue and submitted it as bugreport PPPM-8497.
Thank you.
 
Back
Top