On this submit, we’re going to find out about tips on how to migrate from Godaddy to AWS Route53. First, it’s needed to purchase a site in Godaddy and afterward migrate it to Amazon’s DNS system, which is Amazon Route 53. Switch a Godaddy Area to AWS Route53.
1. Godaddy DNS Administration
Okay, so as soon as we have already got the Godaddy area, we are going to log into our account and entry it to handle our area. On GoDaddy merchandise, we can see the domains we personal, extra merchandise, and suggestions.
On this step, we’re going to click on on the “DNS” button to entry the DNS Administration console from Godaddy. Because the account is new, or nonetheless on Godaddy DNS, we can see completely different sections.
- Information
- Title Servers
- Extra Functionalities
- Forwardings
Okay, that’s numerous data/information and one thing we don’t wish to take a look at right here…
The DNS Administration is in control of routing all of your area site visitors to the required server or out there service, relying in your configuration.
What we truly need to try is the Server Names block. We are going to see that there are 2 nameservers specified within the present Godaddy DNS block.
Normally, Godaddy Title servers are:
- NS#.domaincontrol.com
- NS#.domaincontrol.com
Like these:
These are those to be modified as soon as we’ve created our hosted zone in AWS. Proper now we’re going to go away it as it’s and go to AWS to create our Route 53 hosted zone.
2. AWS
As in Godaddy, we’d like an account on Amazon Net Companies. Make an account right here.
As soon as you’re registered, we’re going to log you into the AWS administration console. There can be a HUGE record of AWS providers. However, DON’T PANIC. We are going to use Route53 that will help you arrange your first hosted zone and migrate your Godaddy Area to AWS Route53.
3. AWS Route 53
Route 53 is without doubt one of the foremost providers of AWS because it provides DNS administration on your domains within the AWS platform. Route 53 could be very helpful as a result of it supplies numerous options, in addition to failover and latency discount performance for a special sort of information.
If you wish to be taught extra about AWS Route53 pricing you possibly can examine it right here.
4. Making a Hosted Zone
What’s a hosted zone? Easy, will probably be the Area Supervisor on Route53 on your personal area. At this level, we’re going to navigate to the Route 53 console and create it. Transferring a site to AWS has many enterprise advantages…including flexibility, redundancy, and extra availability.
a. Route 53 Console
Right here we can create and handle our hosted zones and information and to arrange any area.
b. Create a Hosted Zone
Click on on “Create Hosted Zone” and you will notice a window prompting on the suitable facet. Be certain that to set your zone area with out “www”. In a while, it is possible for you to so as to add information. You can even add feedback in case you want them.
After creating the Hosted zone, you may be redirected to the Hosted Zone set of information, and there it is possible for you to to see the desk with all their information. You’ll discover that there might be NS information and an SOA document.
Observe: We are going to want the NS information to set them in Godaddy.
5. How To Arrange Information
Okay, right here is the tough half, by which we have to copy our current document (if any) on Godaddy with their correct sort, title, and worth.
There could possibly be differing types, however AWS tells you which you’ll set for the required sort. Some examples could possibly be:
- A Document: IPV4 Handle
- CNAME: Canonical Title
- MX: Mail Trade
- TXT: Textual content
- PTR: Pointer
Fast Tip: We would like our domains to be served as quick as doable by means of Amazon’s Route 53, that’s why we have to set the bottom Time to dwell (TTL) doable.
6. Change the DNS
Now could be the time!!
After copying over all our information, we might want to change the Nameservers for those that Amazon offered.
After pointing our new Title Servers to the Route53 hosted zone, we received’t be capable of see the DNS Information resembling IPs, CNAME, or MX Information in Godaddy. As an alternative, we are going to now require going to Route53 to view our setup.
7. Overview Propagation
After altering our DNS, even earlier than altering them, we are able to see the place on this planet it’s propagated and the place it’s lacking.
In the event you check the “NS” and search your area, it’s going to let you know the primary zones the place it’s resolving.
And that’s it. After you could have migrated your Title Servers, it’s only a matter of time earlier than you see the modifications. Now you could have transferred your DNS and area from Godaddy to AWS efficiently. We’re carried out with this Godaddy to AWS Article.
IMPORTANT NOTE: It might take from minutes to 48 hours to see the nameservers migrated relying on the TTL specified.