Article ID: 9651, created on Feb 7, 2011, last review on Aug 12, 2014

  • Applies to:
  • Plesk Expand 2.x

Symptoms

If the DNS zone contains long TXT records like:

google-site-verification=mxk-RreIc_CSepJwW0W1qAcdzYh6USkmMdbb1c6t8Nk

The DNS zone cannot be synchronized with errors like:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?><packet action_id="13349132" version="2.3.2.17"><sync_zone><result><status>error</status><errcode>11119</errcode><errtext>[Operator] Error synchronizing CDNS server. Failed to sync CS server #5: [Generic] Invalid IDN. Domain name is invalid: Label is too long.</errtext><server_id>5</server_id></result><result><status>error</status><errcode>11119</errcode><errtext>[Operator] Error synchronizing CDNS server. Failed to sync CS server #6: [Generic] Invalid IDN. Domain name is invalid: Label is too long.</errtext><server_id>6</server_id></result></sync_zone></packet>

Resolution

Make sure that you are running latest version of Parallels Plesk Expand with all hotfixes installed (including hotfix 7 – Plesk 9.x compatibility hotfix).

Then download file libexpplesk.so for the appropriate architecture (x86 x64) from the attachment, and replace the file /usr/local/expand/lib/libexpplesk.so
Create a copy of the existing file before replacing it.
cp -p libexpplesk.so libexpplesk.so.backup

Finally, restart Parallels Plesk. Expand services and you will be able to synchronize the DNS records.
# /etc/init.d/expandom restart
Stopping expandom:                                         [  OK  ]
Starting expandom:                                         [  OK  ]
# /etc/init.d/expandtm restart
Stopping expandtm:                                         [  OK  ]
Starting expandtm:                                         [  OK  ]

Attachments

0316bb680a7c882e8693bf1bcd23642b 8760abb54be64bdc3c8805b6572624e8 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF