Tonight the easyDNS sysAdmins will be moving “xfr0.easydns.com” (188.8.131.52) between data centres between 8pm EDT and 11pm EDT. During this timeframe, secondary DNS updates will not be possible, nor will external non-easyDNS nameservers slaving customers zones by way of “also-notify” be updated, as “xfr0.easydns.com” will be inaccessible. Once we have the server up and running at the new data centre, we will reload the config on “xfr0.easydns.com” which will grab the latest zone information from the primary nameservers for all zones, and also send out NOTIFYs to external non-easyDNS nameservers should any changes have been made.
We apologise for the late notice and inconvenience with regards to this move, but it is necessary for our infrastructure going forward. It should be noted that NO IP ADDRESSES WILL BE CHANGING. Aside from this short downtime, the service should otherwise be uninterrupted.
[Update – 2014-07-31 @ 12:53am EDT] The maintenance was mostly completed at 11:42pm EDT, yet zones are continuing to catch up. We apologise for going beyond the maintenance window with this, and expect that we should be caught up within the next hour. As always, we thank you for your understanding and your patience!
[Update – 2014-07-31 @ 4:09am EDT] “xfr0.easydns.com” (184.108.40.206) is still catching up with it’s existing zones, and is currently queuing all incoming NOTIFYs that it receives. We apologise for the delay, but this type of event unfortunately occurs when we have to restart a master nameserver, and it subsequently has to load all of the zones it handles. Thankfully, this is a rare event, and we’re both monitoring it’s progress, and hoping that it completes soon. Thank you for your continued patience.
[Update – 2014-07-31 @ 9:06am EDT] At about 5:23am this morning, “xfr0.easydns.com” (220.127.116.11) began to act upon it’s NOTIFY queue, and started pulling in the zones from external masters that sent in their NOTIFYs. This process appears to have taken about 10 minutes, and all zones should be caught up at this time. Thank you for your patience during the unexpectedly long migration of this crucial server, and we apologise for any inconvenience endured.