UPGRADE TO 6.3.2 changes MX Recors


After upgrading a peplink 380 from 6.3.1 to 6.3.2, the upgrade process changes all MX records !
For example if the initial record is mx1.mycompany.com, the records is changed to mx1.mx1

Does anybody face this issue ??

A ticket is opened. Waiting for their feedback.



Hi Paul, we are looking into this at the moment and have found a solution for the reported problem. You did the right thing by logging a ticket, thanks.