To easily GoDaddy Domains with Amazon Web Services (AWS) products such as Elastic Load Balancers, CloudFront, API Gateway, etc., you will need to associate your domain with AWS Route 53.
Follow the step-by-step tutorial below on how to associate your GoDaddy Domain to Amazon Route 53.
For the purpose of demonstration, I will be using my sample domain name –
Setup AWS Route 53 Hosted Zone
Login to AWS Console and then go to Amazon Route 53.
On the welcome screen of Route 53, click on
Get started now.
Create Hosted Zone.
Click again on
Create Hosted Zone.
A sidebar will show asking for you to input the following details about your domain.
|Domain Name:||[Name of your Domain in GoDaddy] (Required)|
|Comment:||[Put your comment here]|
|Type:||Public Hosted Zone|
Then click on
You will then be redirected to the Hosted Zone Record Set page. Two entries are automatically created, NS and SOA Type.
Note the Value of the NS record. This will be used in setting your GoDaddy Domain.
Tip: It is easier to copy the Values on the right side. Do not edit the value of the NS Record.
NS Record means Nameserver Record.
Point GoDaddy Domain to AWS Route 53
Login to your GoDaddy Account and select
DNS on your desired Domain.
In DNS Management, under
Name Servers click on
Custom on the dropdown menu of
Choose your new nameserver type.
Enter the nameservers provided by AWS Route 53 and remove the dot (.) at the end of each line. Then click on
By Default there are only two Nameservers in GoDaddy. You will have to click on
Add Nameserver to accommodate the 4 Nameservers provided by AWS Route 53.
Once that is saved, you may now use your GoDaddy Domain using AWS Route 53 Hosted Zone.
After this you may point the Domain or Subdomains to AWS Services such as EC2 Instances Public IP, Load Balancers, CloudFront, API Gateway and many more services that AWS offers.
Invalid characters found error will happen when you do not remove the dot (.) at the end of the provided nameservers.
I hope the post above helped you in associating your GoDaddy Domain to AWS Route 53. Let me know if you have a different experience on setting this up.