Article ID: 114618, created on Aug 21, 2012, last review on May 10, 2014

  • Applies to:
  • Plesk 11.x for Linux
  • Plesk 10.x for Linux
  • Plesk 9.x for Linux/Unix
  • Plesk 11.x for Windows
  • Plesk 10.x for Windows
  • Plesk 9.x for Windows


The provider is trying to perform a mass synchronization of DNS records with Parallels Plesk Panel (PP) servers managed by PBA-S using the utility. The utility fails to synchronize DNS for some domains and delivers the error message below:

# /usr/sbin/ --hn-id 101
Processing domain domain1.tld... OK
Processing domain domain2.tld... OK
Processing domain domain3.tld... ERROR: Can't use string ("") as a HASH ref while "strict refs" in use at /usr/lib/perl5/site_perl/5.8.8/HSPC/MT/Plesk/ line 3321.


The issue occurs with domains that have aliases in Parallels Plesk Panel. The utility uses the obsolete PP API RPC protocol, e.g., the PP gate is initiated incorrectly when it is invoked from CLI.

PBA-S sends a request to Parallels Plesk Panel to get DNS records of the domain aliases and receives an empty reply because of the outdated protocol.


The issue is going to be fixed in a future product update; for the time being, the workaround below may be applied.

Edit the /usr/sbin/ file on the PBA-S Management Node: Add the following lines after the line "require HSPC::MT::Plesk::DNS;":
use HSPC::MT::Plesk::Protocol::Proto1400;
use HSPC::MT::Plesk::Protocol::Proto1410;
use HSPC::MT::Plesk::Protocol::Proto1411;
use HSPC::MT::Plesk::Protocol::Proto1420;
use HSPC::MT::Plesk::Protocol::Proto1500;
use HSPC::MT::Plesk::Protocol::Proto1520;
use HSPC::MT::Plesk::Protocol::Proto1600;
use HSPC::MT::Plesk::Protocol::Proto1631;
use HSPC::MT::Plesk::Protocol::Proto1632;
use HSPC::MT::Plesk::Protocol::Proto1634;
use HSPC::MT::Plesk::Protocol::Proto1635;

bd7fc88cf1b01f097749ae6f87272128 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 85a92ca67f2200d36506862eaa6ed6b8 dd0611b6086474193d9bf78e2b293040 29d1e90fd304f01e6420fbe60f66f838 400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 6ef0db7f1685482449634a455d77d3f4 aac4a8fcd879de03758354e15495d69a c796c01d6951fa24ed54c7f1111667c6 0a53c5a9ca65a74d37ef5c5eaeb55d7f

Email subscription for changes to this article
Save as PDF