How to Use Amazon Route 53 As DNS Management

How to Use Amazon Route 53 as DNS Management – ​​Basically the server we use uses an IP address to access it, and here DNS functions as a translator, for example we don’t need to remember or share our server address with IP Address but use a domain name that is easy to remember. DNS or Domain Name System, translates human-readable domain names such as judisweb.com to machine-readable IP addresses such as 172.5.23.134.

What is Amazon Route 53?

Amazon Route 53 is a high-availability, broad-scale Domain Name System (DNS) cloud web service. We can use Amazon Route 53 to assist in getting a website or web application up and running.

Amazon Route 53 performs three main functions:

  • Domain name registration
  • Routing Internet traffic to resources for our domain
  • Checking resource health

What is needed?

  • Definitely an AWS account
  • Instances running on EC2 or VPS
  • Set Elastic IP to EC2 Instances
  • Domain name

Step 1: Login AWS Console

If you already have an AWS account, log in to AWS Management Console, if you don’t have an AWS account, please read on tutorial for creating AWS account which I have made.

Step 2: Create DNS Zone Route 53

After logging in to AWS Management Console, All Services > Networking & Content Delivery > Route 53.

Amazon Route 53 Dashboard
Route 53 Dashboard

If you don’t have a domain name, you can register a domain name and purchase a domain name first.

Next create a DNS Zone, in the DNS Management click Create hosted Zone, then enter our domain name, and in the Type choose Public Hosted Zone. Then Create hosted zone.

judisweb route53 createhost
Create hosted zone

Now a set of Nameserver (NS) records will be created and assigned to our domain name.

judisweb route id

Step 3: Configure DNS to the domain

To use the domain can configure with Route 53, we need to update the name server on the domain provider. If the domain registration uses AWS services, you can directly set the nameservers. If the domain registration is elsewhere then we login first to update it.

Screenshot of 20211029 234046077 1
Update Nameservers
Nameservers Value
Nameservers 1 ns-707.awsdns-24.net
Nameservers 2 ns-1654.awsdns-14.co.uk
Nameservers 3 ns-1309.awsdns-35.org
Nameservers 4 ns-193.awsdns-24.com
Nameserver update to Route 53

Step 4: Configure DNS Records

After updating the Nameservers in Step 3, all routes are redirected to Route 53.

Back to Dashboard Hosted Zone then Create Records.

judisweb r53 record
Create Records

These are some common DNS Record parameters that are commonly used for mapping our domain names to EC2 Instances or other services for example CloudFront.

  • A Record – IPv4 addresses, mapping IP hosts to domains.
  • AAA Records – IPv6 addresses, mainly used in HTTP(S), SSL Proxy, and TCP Proxy Load balancing.
  • CNAME – Aliases for one name to another (www.domain.com, pointing to domain.com)
  • MX – Manage where email should be sent.
  • TXT – Any text content, such as domain owner verification text and others

For example to direct users to view the website WordPress on EC2 Instances, we need to make A Record in the DNS Zone.

Then in the Record Type choose A Record, and in the Value field enter the Elastic IP address of the EC2 Instance.

Next to create a www subdomain using CNAME (Canonical Name) to our domain address.

cname dnsrecord
CNAME records

CNAME records not only on the domain that we have but can also use other address domains.

For example using a subdomain that points to CloudFront: shop.domainname.com redirects to xxx.cloudfront.net.

dnsrecord
DNS records



Leave a comment

Your email address will not be published.