Email Service Affected

Please note that this will result in downtime for email services for all customers.

If You Use the highspeedrails.com Nameservers

If we host DNS for your domains (i.e., if you're using our nameservers) you have nothing to worry about and we will take care of ensuring a smooth changeover.

If Your Account is in Seattle and You do NOT Use our Nameservers

If your account is hosted in Seattle and you are not using our nameservers for your domains, please lower TTLs to 600 seconds on all A records pointing to your HSR account. Please do this today and absolutely no later than tomorrow morning before noon PST. The current IP addresses will stop working as soon as each server is moved.

MX Records

If you're not using our nameservers but are using our MX's (mail services), please ensure that you are using a.mx.highspeedrails.com (pri: 0) and b.mx.highspeedrails.com (pri: 10) as your MX records in order to ensure a smooth changeover.

Affected Servers

Affected VPS servers include:

• seattle
• bogota
• luxor
• nassau

Affected customers with managed servers have been emailed individually.

Only Servers in Seattle Affected

This only affects servers in Seattle. This does not affect servers on the east coast.

How to Get the New IP Address

Once the servers have been moved and are online again you can get your account's new IP address, if you need it, by logging in via ssh (to the account hostname, which will not change [see your welcome email]) and running this command (copy and paste):

dnsip `hostname`

Up to 2 Hours of Downtime

Up to 2 hours of downtime per server is expected as a result of the physical move of the servers from one datacenter to another. We will attempt to minimize downtime for the primary mailserver.

Please Subscribe with your Feed Reader

I'll be posting updates to this thread so please subscribe to our RSS feed using your feedreader (Bloglines, Google Reader, etc.). If you're using Firefox 2, this is as easy as clicking on the RSS button in the address bar of your browser.

I realize how inconvenient this will be. Thanks for your patience.

Updates - Jan 5

Hard-Coded IPs

NB: For those affected by this migration, please take note of any cases in which you hard-coded your account's IP address somewhere, for example in a config file, client application, ftp client, svn, client, etc. We hard-code IPs in a few places, which we will take care of updating. If you have hard-coded your IP addresses anywhere, be sure to update it after the migration.

Mailboxers

Mailboxer users who have defined their forwards on the mailserver: We will update the 'script' for you but you will need to update the mtahosts variable of all your mailboxer instances to: 216.10.79.225.

Updates - Jan 6

I found 64 mailboxers on the mailserver, only 5 of which need updating. These have been updated to use the account hostname instead of the IP address.

I believe we have found all the hard-coded ips but if you notice one that needs updating, please let us know.

Migration Complete

The Seattle server move is complete.

The unexpected additional downtime was due to human error on the part of the contractor we hired to configure our Cisco switches, and the resulting time needed to fix it.

I apologize for the inconvenience.

Please check any affected services you use and let us know via email to support@highspeedrails.com if you encounter any problems.

Thanks again for your patience.