• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Wrong DKIM signature after migration

QWeb Ric

Regular Pleskian
Server operating system version
Almalinux 9.3
Plesk version and microupdate number
18.0.60
I'm part way through migrating websites from a CentOS 7.9 server running Plesk 18.0.59 Update #2 to Alma 9 running Plesk 18.0.60, and I've just noticed that if I click through to the mail settings of a transferred website, and then the "How to configure external DNS" link, the DKIM record that it tells me to add to the DNS is different to the original.

I've found a few bug reports of similar, but not quite identical, issues and some of those threads suggest just editing the DNS record on the new server to match the old, but we use external DNS servers and Plesk does appear to be correctly picking that up. It seems to me that the migration maybe isn't pulling the original private keys and is instead just creating new signatures, which then obviously wouldn't match the existing DNS records...

Do I need to actually edit the DNS records, or is there a cleaner way to get Plesk to use the original keys?
 
I do not think that the Plesk Migrator extension does migrate DKIM keys...
So all your domains on the new server will have a different key for the email signature than before.
For domains with local DNS you can most likely just uncheck and then enable the DKIM checkbox again, in order to fix the problem. (as this will align the DNS records with the stored DKIM key)
For external domains you will have to manually change the DNS records for every one of these.
 
I do not think that the Plesk Migrator extension does migrate DKIM keys...
So all your domains on the new server will have a different key for the email signature than before.
For domains with local DNS you can most likely just uncheck and then enable the DKIM checkbox again, in order to fix the problem. (as this will align the DNS records with the stored DKIM key)
For external domains you will have to manually change the DNS records for every one of these.
OK, well at least I know this is expected behaviour then. Bit of a pain but I suppose manageable.
 
Back
Top