AWS Route 53 Domain Name Setup | Configuring DNS with AWS Route53

What is Amzon Route 53?

Amazon Route 53 provides highly available and scalable Domain Name System (DNS), domain name registration, and health-checking web services. It is designed to give developers and businesses an extremely reliable and cost effective way to route end users to Internet applications by translating names like example.com into the numeric IP addresses, such as 192.0.2.1, that computers use to connect to each other. You can combine your DNS with health-checking services to route traffic to healthy endpoints or to independently monitor and/or alarm on endpoints. You can also purchase and manage domain names such as example.com and automatically configure DNS settings for your domains. Route 53 effectively connects user requests to infrastructure running in AWS – such as Amazon EC2 instances, Elastic Load Balancing load balancers, or Amazon S3 buckets – and can also be used to route users to infrastructure outside of AWS.

What can I do with Amazon Route 53?

With Amazon Route 53, you can create and manage your public DNS records. Like a phone book, Route 53 lets you manage the IP addresses listed for your domain names in the Internet’s DNS phone book. Route 53 also answers requests to translate specific domain names like into their corresponding IP addresses like 192.0.2.1. You can use Route 53 to create DNS records for a new domain or transfer DNS records for an existing domain. The simple, standards-based REST API for Route 53 allows you to easily create, update and manage DNS records. Route 53 additionally offers health checks to monitor the health and performance of your application as well as your web servers and other resources. You can also register new domain names or transfer in existing domain names to be managed by Route 53.

What are the DNS server names for the Amazon Route 53 service?

To provide you with a highly available service, each Amazon Route 53 hosted zone is served by its own set of virtual DNS servers. The DNS server names for each hosted zone are thus assigned by the system when that hosted zone is created.

Configuring DNS with Route 53:-

Note that the steps we discuss here are for “simple” DNS configurations, such as hosting a basic website or application. If your current DNS setup is complex, the steps might be slightly different.AWS documentation has a statement that’s worth looking over before we move forward:

“When you migrate DNS service from another provider to AWS Route 53, you reproduce your current DNS configuration in Route 53. In Route 53, you create a hosted zone that has the same name as your domain, and you create records in the hosted zone. Each record indicates how you want to route traffic for a specified domain name or subdomain name.”

In a simple scenario, you migrate one or a combination of the following things from your current DNS provider (in our example, GoDaddy) to AWS:

1. A (Address) records – Associate a domain name or subdomain name with the IPv4 address (for example, 192.0.2.3) of the corresponding resource.

1. AAAA (Address) records – Associate a domain name or subdomain name with the IPv6 address (for example, 2001:0db8:85a3:::abcd:0001:2345) of the corresponding resource.

1. MX (Mail server) records – Route traffic to mail servers.

1. CNAME records – Reroute traffic for one domain to another domain.

Here is the Tutorial video which is based upon Amazon Route 53 Domain Name Setup👇👇

Step 1: Creating a hosted zone

Log in to the AWS Management Console and navigate to the Route 53 menu. Then click on Create a Hosted Zone. Once you create a zone, you will see a form on the right side of the page.Input the following information into the fields:

• Domain Name: Your domain name; in our example, easyaws.com.

• Comment: You can enter whatever you like here.

• Type: Choose depending on what type of availability this zone should be. The default will be “Public Hosted Zone”, which means it can be accessed from the internet. “Private Hosted Zones” are accessible from within AWS VPC and are not available to the public internet.

This step will, by default, create two entries in your hosted zone: NS (nameserver) and SOA (start of authority) records. Take note of the NS (name server) entries. In the next step, we’ll configure these with GoDaddy.

Step 2: Creating DNS Records

Click on the newly created hosted zone, which takes you to the “hosted zone details” screen. Click on Create a Resource Record and you’ll see a new form.Select appropriate values for the following:

• Name: Leave empty if you’re not configuring a subdomain.

• Type: Refer to GoDaddy to find out what your current type is and use the same value here. For setting up a basic website, this will most likely be A or AAAA.

• Alias: Pick an appropriate value. More information on what to pick (and when) is available in this section of AWS documentation.

• Value/Alias Target:  Based on Alias Yes (or) No, you will either point to an IP address or some other Alias entry.

• Routing Policy: “Simple” is the default. But if you want a different routing policy, you may refer to the AWS documentation to understand which one to pick based on the scenario.

Step 3: Managing DNS Settings with your Domain Registrar

In this step, we’re mapping our domain to our server. Going back to our list of the three components of DNS lookup, this mapping helps at the final level. After a request is made to the TLD nameserver, the Amazon nameserver that hosts your records will be returned. This allows users to resolve the domain for your website or application.Log in to the GoDaddy console, navigate to your domains, then click Manage for the domain you want to configure. Next, click Manage DNS under the Additional Settings section (this will be at the bottom of the page):Click on Add (in the Records section at the top of the page) and set the type to NameServer. In the Host field, enter your domain name. In the Points to field, enter one NS IP address from Step 1 when you configured the AWS Hosted Zone record. Repeat this process to add each NS record from the hosted zone in Step 1.That’s it! Your configuration is done! Now, all you need to do is allow some time to have these settings propagated.These same principles will be applicable for cases where you want to leave root domain with GoDaddy but have subdomains DNS on AWS. Apart from “delegation (or) proxying” DNS to AWS, another approach is “transfer the registration”. AWS documentation on Transferring Registration for a Domain to Amazon Route 53 has details about how to do this.

▬▬▬▬▬▬ Connect with me    ▬▬▬▬▬▬ 

Youtube Subscription      ►   https://bit.ly/2LENtS1

Facebook Page:               ► https://www.facebook.com/EasyAWSLearn/

Medium:                          ►  https://techworldwithvijaypatel.mediu...

Dev:                                 ►  https://dev.to/easyawslearn

Telegram Channel:                ►   https://t.me/devtul