Steps to Create a Hosted Zone.
- Login to the AWS Management Console,Navigate to Amazon“Route 53”under“Network & Content Delivery”.
2. Create a Hosted Zone by selecting Create Hosted Zone”and Give the Purchased Domain Name,enter the e comments and choose the Type.We have two types of Hosted Zone, Selecting the Public Hosted Zone now
Public Hosted Zone: A public hosted zone is a container that holds information about how you want to route traffic on the Internet for a domain and its sub domains.
Private Hosted Zone: A private hosted zone is a container that holds information about how you want to route traffic for a domain and its sub domains with in one or more VPC
3. When you created a Hosted Zone,you’ll get two record sets.Those are NS record and SOA record
4. If you purchase the Domain name from any other domain registrar i.e;Godaddy,big rock we have to configure these Name Servers in that account,or we can transfer the domain to AWS.
Now,we are going to create two Web Servers in two different regions and going to configure different routing policies.I’ve choose Mumbai and N.Virginia.
5. Create an EC2 Instance in Mumbai region and connect to the instance.
6. Install httpd package and create html under/var/www/html and start the httpd service and verify the access using public IP address.
7. Create an Elastic Load Balancer and add this EC2 instance to ELB and verify the access using the ELB name.
8. Choose another region(N.Virginia)and perform the same in N.Virginia region also. (Instance launch and ELB creation)
9. Now,we have two web servers in two different regions and we are going to configure routing policies between these two region resources
Simple Routing Policy
This is the default routing policy when you create a new record set.This is most commonly used when you have a single resource that performs a given function for your domain.
10. Select the Create Record Set option,you’ll get an option like below.
a. Give a name for your record set.
b. Choose Type as A–IPV4 address
c. Select Alias record and click on Alias Target option,you’ll get all the available resources under AWS to map your domain with record set. Am selecting Mumbai ELB and selected simple Routing Policy
11. Now all my domain requests should route to Mumbai ELB as this is a simple routing policy and we’ll have single resource for this routing type.
Weighted Routing Policies let you split your traffic based on different weights assigned. Below we have as signed 60% of your traffic to go to AP-SOUTH-1 and 40%to go to US-EAST-1.
Latency based routing allows you to route your traffic based on the lowest network latency for your end user(i.e which region will give them the fastest response time).
To use latency-based routing you create a latency resource record set for the Amazon EC2(or ELB) resource in each region that hosts your website.When Amazon Route 53 receives a query for your site,it selects the latency resource record set for the region that gives the user the lowest latency. Route 53 then responds with the value associated with that resource record set.
Geo location routing lets you choose where your traffic will be sent based on the geographic location of your users (i.e the location from which DNS queries originate).
For example,you might want all queries from Europe to be routed to a fleet of EC2 instances that are specifically configured for your European customers.These servers may have the local language of your European customers and all prices are displayed in Euros.
Fail over routing policies are used when you want to create an active/passive setup.For example you may want your primary site to be in US-East-1 and your secondary DR Site in AP- South-1.
Route 53 will monitor the health of your primary site using a health check. A health check monitors the health of your end points
Multi value answer routing policy
Use when you want Amazon Route 53 to respond to DNS queries with up to eight healthy records selected at random.
More Information :https://www.fgrade.com/aws/