Article ID: 113725, created on Apr 19, 2012, last review on Jun 29, 2016

  • Applies to:
  • Plesk 10.4 for Linux/Unix
  • Plesk 10.4 for Windows

Symptoms

During an upgrade to Parallels Plesk Panel (PP) 10.4.4, DNS records in zones in which the IP address of the main A record is different from the IP address of the domain's hosting, and this domain has subdomains, will be changed.

Cause

There is a bug in the upgrade to version 10.4.4 procedure.

Resolution

Before upgrading to PP 10.4.4, use the Pre-Upgrade Checker to determine which DNS zones on your server will be affected.
 
After upgrading to PP 10.4.4, use the DNS Zone Validation Tool to determine which records were added to or deleted from DNS zones.
Then you will be able to fix these DNS zones manually using the provided information or by using a generated SQL script that allows you to rollback changes that have been made during the upgrade.

You are welcome to discuss the tool in our special thread on the Parallels forum.
 
Output example of Pre-Upgrade Checker:
 
[2012-03-14 08:24:37][INFO] ==> STEP 26: Checking for customized DNS zones which will be modified during upgrade...
[2012-03-14 08:24:37][INFO] A or AAAA records in DNS zone domain.com will be modified or deleted after upgrade.
[2012-03-14 08:24:37][WARNING] A or AAAA records in DNS zones will be modified or deleted after upgrade. Please check
http://kb.sp.parallels.com/en/113725 and /root/plesk10_preupgrade_checker.log for details                              .
[2012-03-14 08:24:37][INFO] Result: Warning
 
Output example of DNS Zone Validation Tool:
 
# php -d safe_mode=0 dns_zone_validator.php

[2012-03-27 01:32:21][INFO] ==> Installed Plesk version/build: 10.4.4 CentOS 5 1013111102.18

[2012-03-27 01:32:21][INFO] ==> Detect system configuration
[2012-03-27 01:32:21][INFO] OS: CentOS release 5.2 (Final)
Kernel \r on an \m
[2012-03-27 01:32:21][INFO] Arch: i386

[2012-03-27 01:32:21][INFO] ==> Validate given db password
[2012-03-27 01:32:21][INFO] Result: OK

[2012-03-27 01:32:21][INFO] ==> Plesk DNS zones validator version: 10.4.0.27
[2012-03-27 01:32:21][INFO] Found pre-upgrade database dump mysql.preupgrade.8.6.0-10.13.4.20120327-083339.dump.gz
[2012-03-27 01:32:21][INFO] Decompressing pre-upgrade database dump to /var/lib/psa/dumps/unpacked_3f7c10c5f773fc2d0af632580ab61b40
[2012-03-27 01:32:21][INFO] Extracting necessary tables to file /var/lib/psa/dumps/prepared_3f7c10c5f773fc2d0af632580ab61b40
[2012-03-27 01:32:21][INFO] Creating temporary database DnsZoneValidator_3f7c10c5f773fc2d0af632580ab61b40
[2012-03-27 01:32:21][INFO] Deleting file /var/lib/psa/dumps/unpacked_3f7c10c5f773fc2d0af632580ab61b40
[2012-03-27 01:32:21][INFO] Deleting file /var/lib/psa/dumps/prepared_3f7c10c5f773fc2d0af632580ab61b40
[2012-03-27 01:32:21][INFO] Following DNS record was deleted from zone domain.com: domain.com. A 10.52.52.105
[2012-03-27 01:32:21][INFO] Following DNS record was deleted from zone domain2.com: ns.domain2.com. A 10.52.52.104
[2012-03-27 01:32:21][INFO] Following DNS record was deleted from zone domain2.com: domain2.com. A 10.52.52.104
[2012-03-27 01:32:21][INFO] Following DNS record was deleted from zone domain2.com: webmail.domain2.com. A 10.52.52.104
[2012-03-27 01:32:21][INFO] Following DNS record was deleted from zone domain2.com: mail.domain2.com. A 10.52.52.104
[2012-03-27 01:32:21][INFO] Following DNS record was deleted from zone domain2.com: sub1.domain2.com. A 10.52.52.104
[2012-03-27 01:32:21][INFO] Following DNS record was added to zone domain2.com: domain2.com. A 10.52.52.104
[2012-03-27 01:32:21][INFO] Following DNS record was added to zone domain2.com: ns.domain2.com. A 10.52.52.105
[2012-03-27 01:32:21][INFO] Following DNS record was added to zone domain2.com: mail.domain2.com. A 10.52.52.105
[2012-03-27 01:32:21][INFO] Following DNS record was added to zone domain2.com: webmail.domain2.com. A 10.52.52.105
[2012-03-27 01:32:21][INFO] Following DNS record was added to zone domain2.com: sub1.domain2.com. A 10.52.52.105
[2012-03-27 01:32:21][INFO] Deleting temporary database DnsZoneValidator_3f7c10c5f773fc2d0af632580ab61b40
[2012-03-27 01:32:21][INFO] For fix this records directly in database you can use SQL file: /root/fix_dns_records.sh

Found errors: 0; Found Warnings: 0

[root@a10-52-52-104 ~]#
 
The script generates a shell file with commands that fix the described changes.

Limitation

If DNS records that were changed by the upgrade are removed or modified manually before running the script, the script will offer the option to add such records to the zone (which did not exist at the time of the script start-up), as they were before the upgrade.
 

Attachments

56797cefb1efc9130f7c48a7d1db0f0c e8756e9388aeca36710ac39e739b2b37 a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 dd0611b6086474193d9bf78e2b293040 ff5a00b8ead2e480367b019417a04207 85a92ca67f2200d36506862eaa6ed6b8 c796c01d6951fa24ed54c7f1111667c6

Email subscription for changes to this article
Save as PDF