Symptoms
-
A subscription example.com is migrated between two Plesk servers.
-
The following error is returned after the post-migration check of the migrated subscription:
Post-migration checks
The DNS server at 203.0.113.2 returned incorrect DNS records. Here is the difference:
expected 'default._domainkey.example.com. TXT v=DKIM1; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDxHiIayxdVAy0BDmv+W/6+hUHoDPfzgPc2DFqubFraw8C2zyuudKJtMFAp3OiogVCntMU+7WwQ3wbBS6q9mNy5F8KHHdy9hTMjjrMCRpkzylAVPVvaoAZFBIPDyTDT+0rmx9sIEkGUoliWdpHceePNgtxn9oXbvlE1BTzKz9OtVwIDAQAB;', got 'default._domainkey.example.com. TXT v=DKIM1; p=DKIM1; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDxHiIayxdVAy0BDmv+W/6+hUHoDPfzgPc2DFqubFraw8C2zyuudKJtMFAp3OiogVCntMU+7WwQ3wbBS6q9mNy5F8KHHdy9hTMjjrMCRpkzylAVPVvaoAZFBIPDyTDT+0rmx9sIEkGUoliWdpHceePNgtxn9oXbvlE1BTzKz9OtVwIDAQAB;'
Make sure that:
1. The DNS zone of this domain exists in target Plesk and is enabled.
2. All desired DNS records exist in target Plesk and are active.Ignore this warning if you have changed DNS zone after migration and the resolved records look fine.
-
If compare the TXT DNS record for the hostname default._domainkey.example.com on the source and target servers in the menu Domains > example.com > DNS Settings, they are indeed different - the additional text
p=DKIM1;is present to the record on the target server.Manual querying confirms that:
-
Source server:
# host -t TXT default._domainkey.example.com 203.0.114.1
Using domain server:
Name: 203.0.114.1
Address: 203.0.114.1#53
Aliases:default._domainkey.example.com descriptive text "v=DKIM1; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDxHiIayxdVAy0BDmv+W/6+hUHoDPfzgPc2DFqubFraw8C2zyuudKJtMFAp3OiogVCntMU+7WwQ3wbBS6q9mNy5F8KHHdy9hTMjjrMCRpkzylAVPVvaoAZFBIPDyTDT+0rmx9sIEkGUoliWdpHceePNgtxn9oXbvlE1BTzKz9OtVwIDAQAB;"
-
Target server:
# host -t TXT default._domainkey.example.com 203.0.113.2
Using domain server:
Name: 203.0.113.2
Address: 203.0.113.2#53
Aliases:default._domainkey.example.com descriptive text "v=DKIM1; p=DKIM1; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDxHiIayxdVAy0BDmv+W/6+hUHoDPfzgPc2DFqubFraw8C2zyuudKJtMFAp3OiogVCntMU+7WwQ3wbBS6q9mNy5F8KHHdy9hTMjjrMCRpkzylAVPVvaoAZFBIPDyTDT+0rmx9sIEkGUoliWdpHceePNgtxn9oXbvlE1BTzKz9OtVwIDAQAB;"
-
Cause
The bug in the Plesk Migrator extension PMT-4640. It is planned to be fixed in one of the next versions of the extension.
Resolution
Until the bug is fixed, as workarounds:
Plesk GUI workaround
-
Log into Plesk on the target server.
-
Go to Domains > example.com > DNS Settings.
-
Edit the TXT record default._domainkey.example.com so it looks like follows:
default._domainkey.example.com. TXT v=DKIM1; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDxHiIayxdVAy0BDmv+W/6+hUHoDPfzgPc2DFqubFraw8C2zyuudKJtMFAp3OiogVCntMU+7WwQ3wbBS6q9mNy5F8KHHdy9hTMjjrMCRpkzylAVPVvaoAZFBIPDyTDT+0rmx9sIEkGUoliWdpHceePNgtxn9oXbvlE1BTzKz9OtVwIDAQAB;
Bulk workaround over CLI
-
Connect to the Plesk server via SSH.
- Backup Plesk database.
-
Create a list of DNS zone ids where "p=DKIM1;" is found:
# plesk db -N -e "select dns_zone_id from psa.dns_recs where displayHost like 'default._domainkey.%' and (val like '% p=DKIM1;%' or displayVal like '% p=DKIM1;%');" >> dns_zone_ids.txt
-
Verify if the domain names are the migrated ones which need the correction:
# for id in `cat dns_zone_ids.txt`; do plesk db "select dz.name, dz.id from dns_zone as dz where dz.id=$id;";done
-
Based on the output of step 4, remove…
with