Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

How to Migrate DNS from GoDaddy to AWS Route53

DZone's Guide to

How to Migrate DNS from GoDaddy to AWS Route53

Take a loo at this article which will show you how you can change your GoDaddy domain name for added speed and availability.

· Cloud Zone ·
Free Resource

Insight into the right steps to take for migrating workloads to public cloud and successfully reducing cost as a result. Read the Guide.

I figured it would be a great idea to make a quick migration guide for you. In this blog, we are going to learn about how to migrate from GoDaddy to AWS Route53. First, is necessary to buy a domain in GoDaddy and later on migrate it to Amazon’s DNS system, which is Amazon Route 53. Transfer a GoDaddy Domain to AWS Route53.

First things first. In case you do not own a domain yet, you should buy one. Check this blog to learn how to do it.

GoDaddy DNS Management

Okay, so once we already have the GoDaddy domain, we will log into our account and access to manage our domain. On GoDaddy products we will be able to see the domains we own, additional products, and recommendations.

In this step, we are going to click to the “DNS” button to access the DNS Management console from GoDaddy. Since the account is new, or still on GoDaddy DNS, we will be able to see different sections.

Okay, that’s a lot of information/records and something we don’t want to look at here…

The DNS Management is in charge of routing all your domains traffic to the specified server or available service, depending on your configuration.

What we actually want to take a look at is to the Server Names block. We will see that there are 2 nameservers specified in the current GoDaddy DNS block.

Usually, GoDaddy Name servers are:

  1. NS#.domaincontrol.com
  2. NS#.domaincontrol.com

Like these:

These are the ones to be changed once we have created our hosted zone in AWS. Right now we are going to leave it as it is, and go to AWS to create our Route 53 hosted zone.

AWS

As in GoDaddy, we need an account on Amazon Web Services. Make an account here.

Once you are registered, we are going to log you into the AWS management console. There will be a huge list of AWS services. But don’t panic; we will use Route53 to help you set up your first hosted zone and migrate your GoDaddy Domain to AWS Route53.

Route 53 is one of the main services of AWS since it offers the DNS management for your domains in the AWS platform. Route 53 is very useful because it provides a lot of features, as well as failover and latency reduction functionality for a different type of records.

If you want to learn more about AWS Route53 pricing you can check it here.

Creating a Hosted Zone

What is a hosted zone? Simple, it will be the Domain Manager on Route53 for your own domain. At this point, we are going to navigate to the Route 53 console and create it. Transfering a domain to AWS has many business benefits; for example, it adds flexibility, redundancy and more availability.

Route 53 Console

Here we will be able to create and manage our hosted zones and records and to setup up any domain.

Click on “Create Hosted Zone” and you will see a window prompting on the right side. Make sure to set your zone domain without “www.” Later on, you will be able to add records. You can also add comments in case you need them.

After creating the Hosted zone, you will be redirected to the Hosted Zone set of record, and there you will be able to see the table with all their records. You will notice that there will be NS records and an SOA record.

Note: We will need the NS records to set them in GoDaddy.

How to Set up Records

Okay, here is the tricky part, in which we need to copy our existing record (if any) on GoDaddy with their proper type, name and value.

There could be different types, but AWS tells you which you can set for the specified type. Some examples could be:

A Record: IPV4 Address
CNAME: Canonical Name
MX: Mail Exchange
TXT: Text
PTR: Pointer

Quick Tip: We want our domains to be served as fast as possible through Amazon’s Route 53, so that’s why we need to set the lowest Time to Live (TTL) possible.

Now is the time!!

After copying over all our records, we will need to change the Nameservers for the ones that Amazon provided.

After pointing our new Name Servers to the Route53 hosted zone, we won’t be able to see the DNS Records such as IPs, CNAME or MX Records in GoDaddy. Instead, we will now require going to Route53 to view our setup.

Review Propagation

After changing our DNS, even before changing them we can see where in the world it is propagated and where it is missing.

If you test the “NS” and search your domain, it will tell you the main zones where it is resolving to.

And that’s it. After you have migrated your Name Servers, it is only a matter of time to see the changes. Now you have transferred your DNS and domain from GoDaddy to AWS successfully. We are done with this GoDaddy to AWS Article.

Important note: It can take up from minutes to 48 hours to see the nameservers migrated depending on the TTL specified.

TrueSight Cloud Cost Control provides visibility and control over multi-cloud costs including AWS, Azure, Google Cloud, and others.

Topics:
aws ,godaddy ,route53 ,cloud ,migration ,tutorial

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}