DNS Zone Validation Tool

Applies to:

Plesk 10.4 for Linux/Unix

Plesk 10.4 for Windows

Symptoms

Amid a upgrade up to Parallels Plesk Panel (PP) 10.4.4, DNS records in zones in which the IP location of the primary A record is not quite the same as the IP location of the domain hosting, and this domain has subdomains, will be changed.

Cause

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

Resolution

Before moving up to PP 10.4.4, utilize the Pre-Upgrade Checker to figure out which DNS zones on your server will be influenced.

In the wake of upgrade to PP 10.4.4, utilize the DNS Zone Validation Tool to figure out which records were added to or erased from DNS zones.

At that point you will have the capacity to alter these DNS zones manually utilizing the given data or by utilizing a generated SQL script that permits you to rollback changes that have been made amid the update.

Output example of Pre-Upgrade Checker:

[INFO] ==> STEP 26: Checking for customized DNS zones which will be modified during upgrade…
[INFO] A or AAAA records in DNS zone domain.com will be modified or deleted after upgrade.
[WARNING] A or AAAA records in DNS zones will be modified or deleted after upgrade.
[INFO] Result: Warning

Output example of DNS Zone Validation Tool:

# php -d safe_mode=0 dns_zone_validator.php
[INFO] ==> Installed Plesk version/build: 10.4.4 CentOS 5 1013111102.18
[INFO] ==> Detect system configuration
[INFO] OS: CentOS release 5.2 (Final)
Kernel \r on an \m
[INFO] Arch: i386
[INFO] ==> Validate given db password
[INFO] Result: OK
[INFO] ==> Plesk DNS zones validator version: 10.4.0.27
[INFO] Found pre-upgrade database dump mysql.preupgrade.8.6.0-10.13.4.20120327-083339.dump.gz
[INFO] Decompressing pre-upgrade database dump to /var/lib/psa/dumps/unpacked_3f7c10c5f773fc2d0af632580ab61b40
[INFO] Extracting necessary tables to file /var/lib/psa/dumps/prepared_3f7c10c5f773fc2d0af632580ab61b40
[INFO] Creating temporary database DnsZoneValidator_3f7c10c5f773fc2d0af632580ab61b40
[INFO] Deleting file /var/lib/psa/dumps/unpacked_3f7c10c5f773fc2d0af632580ab61b40
[INFO] Deleting file /var/lib/psa/dumps/prepared_3f7c10c5f773fc2d0af632580ab61b40
[INFO] Following DNS record was deleted from zone domain.com: domain.com. A 10.52.52.105
[INFO] Following DNS record was deleted from zone domain2.com: ns.domain2.com. A 10.52.52.104
[INFO] Following DNS record was deleted from zone domain2.com: domain2.com. A 10.52.52.104
[INFO] Following DNS record was deleted from zone domain2.com: webmail.domain2.com. A 10.52.52.104
[INFO] Following DNS record was deleted from zone domain2.com: mail.domain2.com. A 10.52.52.104
[INFO] Following DNS record was deleted from zone domain2.com: sub1.domain2.com. A 10.52.52.104
[INFO] Following DNS record was added to zone domain2.com: domain2.com. A 10.52.52.104
[INFO] Following DNS record was added to zone domain2.com: ns.domain2.com. A 10.52.52.105
[INFO] Following DNS record was added to zone domain2.com: mail.domain2.com. A 10.52.52.105
[INFO] Following DNS record was added to zone domain2.com: webmail.domain2.com. A 10.52.52.105
[INFO] Following DNS record was added to zone domain2.com: sub1.domain2.com. A 10.52.52.105
[INFO] Deleting temporary database DnsZoneValidator_3f7c10c5f773fc2d0af632580ab61b40
[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

On the off chance that DNS records that were changed by the upgrade are modified or altered physically before running the script, the script will offer the alternative to add such records to the zone (which did not exist at the time of the script start-up), as they were before the update.