At approximately 11:30am CST today we encountered an issue with our DNS services being imported into the new ServerBeach portal. This may be causing an interruption for certain domains that are hosted on the GeoDNS servers.

We are currently working diligently to correct this issue and will provide an update when DNS services are fully functional.

All of us at ServerBeach sincerely regret the inconveniences associated with this incident, and will fully stand behind our Service Level Agreement. We apologize for this disruption and thank you for your continued patronage and understanding.

If you have any questions regarding this issue, please open an online ticket at https://my.serverbeach.com/ or contact our support team at 1-800-741-9939.

Thank you.

__________________
Charnell Lucich
Community Evangelist

ServerBeach | By Geeks, For Geeks

Twitter: @CharnellLucich

At this time, DNS issues have been resolved. Customers may still see some truncated data in their customer portal and this will be corrected within the next 24 hours.

If you have any questions regarding this issue, please open an online ticket at https://my.serverbeach.com/ or contact our support team at 1-800-741-9939.

We apologize for this disruption and thank you for your continued patronage and understanding.

__________________
Charnell Lucich
Community Evangelist

ServerBeach | By Geeks, For Geeks

Twitter: @CharnellLucich

We are currently aware that customers running private nameservers that rely on GeoDNS for slave services are not working correctly. Our engineers are working quickly to resolve this issue.

Thank you for your continued patience.

__________________
Charnell Lucich
Community Evangelist

ServerBeach | By Geeks, For Geeks

Twitter: @CharnellLucich

We have no updates at this time but we are continuing to address the issues and have made progress. More updates to come as they become available.

__________________
Charnell Lucich
Community Evangelist

ServerBeach | By Geeks, For Geeks

Twitter: @CharnellLucich

Progress is continuing to be made. We apologize for this disruption and thank you for your continued patronage and understanding.

__________________
Charnell Lucich
Community Evangelist

ServerBeach | By Geeks, For Geeks

Twitter: @CharnellLucich

Our internal systems have been updated to address the issues that started the issues earlier this afternoon. Due to complexities of SuperDNS, these updates are going to take a few minutes to hours to accomplish. Unfortunately, we do not have an exact ETA, but the fixes have been made and are propagating out at this time.

If you are still having issues, please update your support tickets so our techs can quickly assist you.

Thank you for your patience.

__________________
Charnell Lucich
Community Evangelist

ServerBeach | By Geeks, For Geeks

Twitter: @CharnellLucich

Dear ServerBeach Customer,

Recently we made some upgrades and changes to systems to offer our customers a more robust offering with DNS and account management. During this process, unfortunately, we did encounter some problems during the migration.

During our initial data import, some domain records were corrupted in our database. The corruption resulted in truncated/incorrect A records within the domains. To resolve the issue, we chose to re-import the correct A records and eliminate truncated/incorrect A records in two passes. By breaking the work into two steps, we were able to restore functionality quickly and ensure that we didn’t remove any valid A records during our clean up effort.

From the start, we’ve had a dedicated team working to restore service to the 450 affected customers. Currently, we have nine people working exclusively reviewing customer tickets to ensure we’ve captured all of the outstanding issues. At this point we have two areas we’re still addressing:

1. Secondary Zones NOT Updating
We are seeing some domain transfers being rejected by our new DNS service. If you are experiencing a DNS outage, please check the following:

• If your registrar requires an IP for the authoritative name servers in addition to the host names, you will need to provide your registrar with the updated IP address. Most registrars now ask for nameserver host names only. For example, they will require that you enter ns1.geodns.net and ns2.geodns.net for master and slave systems. However, if you were required to provide an IP address as well, the IP will need to be modified for ns2.geodns.net.
  
• If you have your own name servers configured as slaves to the GeoDNS name servers, you will need to edit your name server configuration files specifying the new IP address listed above. If you have name servers configured as masters for your domain(s), use ns2.geodns.net as a slave and have ACLs setup, you will have to modify them accordingly. You will want to make sure that the following two IP addresses are configured in your DNS as a slave and that no ACLs are preventing them from transferring your zones. The IP addresses are 69.90.252.22 and 64.34.249.156.
  
• If you have name servers configured as masters for your domain(s), use ns2.geodns.net as a slave and have hard coded the IP address within your zone files, you will have to modify them accordingly with the new IP address above.

If you’re still having problems after doing the above, please open a support ticket.


2. Data Clean Up
At this point, Phase One, the import of correct A records is complete. Your domain’s zone file should contain all the necessary records to provide the functionality you require. We have completed a test run of Phase Two, elimination of the truncated/incorrect A record will proceed today. We are currently reviewing all of the data the script will remove from the database. Once we are sure it is going to do what we expect, we’ll kick it off. The script will take about 24 hours to complete the cleanup.

If you need additional assistance, please feel free to contact us at 1-800-741-9939.

__________________
Charnell Lucich
Community Evangelist

ServerBeach | By Geeks, For Geeks

Twitter: @CharnellLucich