Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
With GoDaddy’s entire DNS service down, I figured it would be a good time to write up a quick migration guide for anyone looking to use this opportunity to jump the GoDaddy ship. This guide assumes that your domain name is with another registrar, and you are only using GoDaddy for hosting. If your domain name itself is controlled through GoDaddy, you’re out of luck until they come back online.
The Progress Kinvey infrastructure relies heavily on Amazon Web Services (AWS) for other components, so Route 53 seemed like a natural choice first choice to cover.
To start, log into the Route 53 dashboard in the AWS Console.
As the landing page describes, your first step is to create a “hosted zone.” A hosted zone is a concept created by Amazon to describe a collection of DNS records (i.e. A records, CNAME records, MX records) that are managed together under a single parent domain name (i.e. www.davewasmer.com, blog.davewasmer.com, etc). You can use the Route 53 dashboard to manage these hosted zones. For a good explanation of the different types of DNS records, check out Google’s guide.
Go ahead and click “Create Hosted Zone,” and fill in your domain name in the form that appears on the right:
This next part is important. When you created the hosted zone for your domain, Route 53 filled in some basic DNS records. To see them, select your domain name from the list, and click “Go to Record Sets” in the top right:
You’ll see that Route 53 populated your domain with a set of NS records and SOA records.
Here is the important bit: your current site may have extra DNS records needed.
For example, if you host a blog on Tumblr, and blog.davewasmer.com leads to it, you probably have a CNAME record setup to create that link. Also, if you recieve email at your domain (firstname.lastname@example.org), you probably have an MX record set for that.
Quickly make a list of all these extra records you’ll need, and add them now (use the “Create Record Set” button):
Finally, it’s time to make the switch. Head over to your current registar, and change the nameservers from the GoDaddy addresses to the ones provided in the NS record set on your Route 53 dashboard.
Note: because DNS servers around the world cache this value, it may take some time to see the change work while the update propogates through the DNS system.
Dave is an Ember.js developer and economist with nine years of experience in the field. He is the creator of Denali JS, a layered conventions Node.js framework for building ambitious APIs.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.