1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Plesk 2.3.1 migration "bug"

Discussion in 'Plesk Expand 2.3 Troubleshooting Issues' started by AndreasK, Sep 23, 2008.

  1. AndreasK

    AndreasK Regular Pleskian

    26
    23%
    Joined:
    Sep 6, 2006
    Messages:
    173
    Likes Received:
    0
    Hello,

    we have noticed an issue or bug on Plesk Expand 2.3.1 when we try to migrate a client from server A to server B. Each server has his own mailserver:

    After the migration the DNS settings of a domain do not refresh completely to the new adress. The A record is correct, it shows to the server where we just migrated the client. But the MX-record shows to the "old" mailserver IP Adress. So after the confirmation of the migration, the client is deleted on the "old" mailserver. With these DNS settings it is not possible for the client to receive mails with the new mailserver.

    Is this a "bug" or is it the "intention" of the migration that it keeps the "old" MX-record (EG because the client could use his own MX-server)?

    After the migration we had to restore the default dns settings for each domain. But this is very much work if we migrate hundreds of clients.

    Thank you & best regards

    Andreas
     
  2. gold

    gold Regular Pleskian

    25
    57%
    Joined:
    Jan 8, 2008
    Messages:
    307
    Likes Received:
    0
    Thanks you for your the bug report. It will be fixed.
     
Loading...