Steps to Configure Route53
To configure our domain with AWS route53, we have the following steps:
Creating Hostzone in AWS Route53
- Sign in to AWS Console
- Create HostedZone
- Integrating Route53 with Domain Registrar
- Creating DNS records
Let’s go for setting up.
Step 1: Sign in to the AWS Management Console
Open Route53 in AWS Console by visiting “https://us-east-1.console.aws.amazon.com/route53/v2/hostedzones#”
From this page we can create hostedzones and manage them to add/update records.
Step 2: Create Hostedzone in Route53
You can think of this hosted zone as a directory, it represents a collection of records that can be managed together, belonging to a single parent domain name.Create a hosted zone with the same name as your domain and then create records in the hosted zone to tell Amazon Route 53 how to route traffic.
- Click on Create Host Zone.
- Fill the Hosted Zone details as mentioned below
- Domain Name: Your owned Domain Name (if not exists you can buy one from Route53 itself)
- Description: Readable text to identify the domain
- Type: Choose public if you wanna route traffic on the internet, and private if you wanna route traffic inside AWS VPC.
Step 3: Integrating Route53 with Domain Registrar
You can find your route53 nameservers on the hosted zone page, copy all 4 nameservers, and update them on the Domain registrar website.
Step 4: Creating DNS Records.
After opening the Hosted Zones Page, click on Create Record, and fill in the record details as mentioned below:
- Record Name: Domain/subdomain for the record
- Record Type: Choose the type of the record based on your use case, here are the record types used often.
Record Type |
Description |
---|---|
A |
Routes traffic to an IPv4 address and some AWS resources Choose when routing traffic to AWS resources for EC2, API Gateway, Amazon VPC, CloudFront, Elastic Beanstalk, ELB, or S3. For example: 192.0.2.44. |
AAAA |
Routes traffic to an IPv6 address and some AWS resources Choose when routing traffic to CloudFront distributions (when IPv6 is enabled) or ELB load balancers. For example 2001:0db8::8a2e:0370:bab5. |
CNAME |
Routes traffic to another domain name and to some AWS resources Choose when routing traffic to some Elastic Beanstalk environments or to Amazon RDS database instances. |
MX |
Specifies mail servers Choose to specify the domain names of your mail servers. For multiple servers, you can also specify a priority for each one. |
TXT |
Used to verify email senders and for application-specific values Choose instead of SPF, or when you want Route 53 to return application-specific values. |
- Alias: If you wanna create a record as an alias of existing AWS-supported resources like Cloudfront endpoint, S3 Website, and EC2 Instance, then you can check this option and choose the appropriate endpoint in sub-options.
- Value: Value of the destination to route traffic to, for example, if you choose routing type A, the value is IP Address, for CNAME it’s domain URL
- TTL: The amount of time, in seconds, that you want DNS recursive resolvers to cache information about this record, the ideal time would be 300.
TTL reflects the time to reflect the changes (a new ip address, a new domain in value), so client will get updated destination after specified TTL
How To Configure Amazon Route 53 In AWS
In this article, we’ll learn the basics of DNS management, and how to configure our domain with AWS Route53, add DNS records, customize the attributes in DNS records, monitor the health status of the record, and make our site live.