AWS Route 53

Amazon Route 53

Amazon Route 53 is a highly available and scale-able Domain Name System (DNS). Domain name is simply the name of your website.
It’s a global service and supports IPv6.

One can register a domain name for their website using Route 53. When you register a domain, it creates a hosted zone with the same name as the domain and assigns 4 sets of Name Servers (unique to the account).

if a website is hosted in AWS, Route 53 will connect the traffic to your web server when the user enters your domain name in the internet.

Route 53 checks health of the resource (web server) through automatic requests to the resource before connecting to the server.

When you host your domain with AWS, Route 53 will completely manage your domain.

Connect the domain to the Route 53 Hosted Zone.
Update your domain registrar with the correct Name Servers for your Route 53 Hosted Zone.
Doing this means Route 53 DNS service will be serving DNS traffic for the domain of the Hosted Zone.
If you register a domain with the different registrar, you need to configure the Route 53 NS server list in your registrar DNS database for your domain.
You can use Route 53 as the DNS service for any domain, even if the TLD for the domain is not included in the supported TLD list.
By default, SOA & NS records will be created in the Hosted Zone.

This is the most common routing policy where the internet traffic is routed to a single resource or a server.

In this type of routing, you can define the weightage of internet traffic to a specific server.
For example, if you have two web servers (one located in US East and another one in US West), you can set the routing weightage either equally to both the servers or set unequal distribution, depending upon your case.
If it is set equally, the first request may receive the IP address of server 1 while the second request may receive the IP of server 2.

When you have servers in multiple locations, you may want to provide the response with least latency.
When you select this policy, you would need to create latency records for your resources in different regions.
When the request comes from the internet, route 53 evaluates the latency records and selects the server that has the least latency.

As its name implies, the routing of traffic is based on user’s location/region.
Let's assume you have 2 web servers (one in US and other in Asia).
When you set this routing policy, the internet traffic for users from US locations is automatically routed to the server located in US and to Asia server for all Asian traffic.

In this type of routing, the user traffic is routed to the location of the resources.
For example, if you have web servers only in the US and UK. If the user traffic comes to France, this traffic is routed to the UK server as this server is in the nearest proximity of the user location.
In other cases, let's assume that you have 3 servers (1 in US, 1 in UK and 1 in France). If you take down the France server temporarily for some reason, you may route the traffic from the France region to the UK server as it is closer to France.

If you have multiple servers and if one of the servers fails for some reason, the traffic is immediately routed to another server.
This is commonly used in DR scenarios where the traffic is routed to the secondary server when the primary server is unhealthy.

This policy is similar to Simple routing policy but this is used when there are many web servers present.
When traffic hits the website, Route 53 sends the requests to multiple servers or load balancers and the response is received in random order from any IP address. This means, when a request is sent next time, the response may be received from a different IP address.

These are called containers that hold information about how you want to route your internet traffic for your website. There are two types of Hosted Zones such as:

This is to set information about how you want to route your internet traffic to the publicly hosted website.
When you register a domain with AWS, the hosted zone is automatically created by AWS. If you transfer your already registered domain, then you would need to manually create a hosted zone.

This is a container that holds information about how you want to route traffic within one or more VPCs created with Amazon VPC service.

The below picture illustrates how Route 53 works when a user enters a website name in the internet browser to the point the web page is rendered. Below the picture are sequences of steps that happen in the process.

User requests for a website in the web browser which is sent to DNS resolver
DNS Resolver sends the request for domain name to DNS root name server
DNS root name server responds to DNS resolver to go to Name Server for .com TLD
DNS Resolver sends the domain name to name server for .com domain
Name server responds to DNS resolver with 4 Route 53 name servers for the associated website.
DNS Resolver sends the request for website name to one of 4 Route 53 name servers.
Route 53 name server responds back with the IP for the website from the hosted zone.
DNS resolver supplies the IP address to the web browser.
Web browser sends the request for website to the supplied resource (web server).
Web Server in this IP address renders the web page to the web browser.

Page updated

Google Sites

Report abuse