Pixel Server Migration
This blog post is only relevant to users of the MXroute service who have been provisioned on the pixel.mxrouting.net server. If you are not on the pixel.mxrouting.net server, this blog post is not intended for you. If your DNS records are otherwise pointing to "lisa.mxrouting.net" you are also fine, that legacy hostname will remain in place and not be changed.
This message is to inform you that we are in the process of migrating the server to a new hardware infrastructure. While we do not know exactly how long this process will take, we will keep you informed of any updates along the way. When the event nears completion, we will post a status update here: https://status.mxroute.com
As we near the end of the migration, there will be a brief interruption of services on the server. For users that have properly configured DNS servers on their network, the outage will appear to be nothing more than a hiccup. However, for users who have misconfigured DNS servers on their network, it may take an unknown amount of time for their systems to pick up the DNS change when the migration is complete.
At every turn we have encouraged users to use CNAME and MX records for any DNS records pointing to the pixel.mxrouting.net server. However, we realize that some users may be using A records (and only for mail and webmail custom subdomains, there would otherwise be no reason to have any A record pointing to the server). Therefore, we strongly recommend that users who have A records pointed to the server should remove them, and replace them with CNAME records to ensure a smooth transition to the new hardware infrastructure. This is not applicable to MX records, those are already fine.
Please note that the new server IP will be 22.214.171.124. This information will be useful for users who need to update their DNS records.
We apologize for any inconvenience this may cause, and we will make every effort to minimize downtime and ensure a smooth transition to the new hardware infrastructure. If you have any questions or concerns about the migration process, please do not hesitate to open a ticket at the link below.
Thank you for your understanding and cooperation.