Route53

• Route53 is a highly available and scalable domain name systems(DNS)

web services. Route53 connect user requests to internet applications
running on AWS or on-premises.
• Route53 name server searches the DNS zone for the domain.com IP
address and other relevant information and returns it to the DNS
resolver.
• ISP
• Cache
• Domain registration
• Domain hosting
• Domain management
• Heath checks
• Routing policies
• 1. simple routing policy
• 2. multi-value routing policy
• 3. geo-location routing policy
• 4. latency routing policy
• 5. weighted routing policy
• 6. fail-over routing policy
• 7. IP-based routing policy
• “cloudping.info”
• www.domain.com routingpolicy A mumELB

• 1. simple routing policy

• www.domain.comSRP A mumELB
• www.domain.comSRP A ohioELB(denied)
• 2. Multi-value routing policy (up to 8 records)
• www.domain.comMRP A IP1
• www.domain.comMRP A IP2
• 3. Geo-location routing policy
• Geo.domain.com GRP USA A mumELB
• Geo.domain.com GRP ASIA A ohioELB
• 4. Latency routing policy
• Lat.domain.com LRPap-south-1A mumELB
• Lat.domain.com LRPus-east-1 A ohioELB
• [ cloudping.info ]
• 5. Weighted routing policy
• Weight.domain.com WRP 3 on-premise
• Weight.domain.com WRP 1 aws
• 6. Fail-over routing policy
• Fail.domain.com FRP primary A ohio (health check)
• Fail.domain.com FRP secondary mum
• 7. IP-based routing policy
• Ip.domain.com IRP 10.0.0.0/8 mum
• Ip.domain.com IRP 12.0.0.0/8 ohio
• 1. simple routing policy 
• A simple routing policy is round-robin policy and can be applied when there is a single
resource during the function for the domain e.g. web server that servers content for the
website.
• Simple routing policy helps configure standard DNS records, with no special Route
53nrouting such as weighted or latency.
• If you choose the simple routing policy in the Route 53 console, you can't create multiple
records that have the same name and type, but you can specify multiple value in the same
record.

• 2. weighted routing policy 

• Weighted routing policy is used when there are multiple resources for the same
functionality and the traffic needs to be split across the resources based on some
predefined weights.
• Weighted routing allows you to associate multiple resources with a single domain name
(example.com) or subdomain (acme.example.com) and choose the amount of traffic routed
for each resource. This can be useful for a variety of purposes, including load balancing and
testing new versions of software.
• 3. Geo-location routing policy
• Geolocation routing policy is used to route the traffic based on the geographic location
from where the DNS query is originated.
• This policy allows to send the traffic to resources in the same region from where the
request was originated i.e. It allows to have site affinity based on the location of the
user.
• Use when you want to route traffic based on the location of your users.
• 4. Latency routing policy
• To use latency-based routing, you create latency records for your resources in multiple
AWS Regions. When Route 53 receives a DNS query for your domain or subdomain
(example.com or acme.example.com), it determines which AWS Regions you've created
latency records for, determines which region gives the user the lowest latency, and then
selects a latency record for that region. Route 53 responds with the value from the
selected record, such as the IP address for a web server.
• Use when you have resources in multiple AWS regions and you want to route traffic to
the region that provides the best latency.
• 5. fail over routing policy
• Create health check first, Use load balancer domain name in health check configuration
• Failover routing allows you to route traffic to a resource when the resource is healthy or
to a different resource when the first resource is unhealthy.
• Primary and secondary records can route traffic to any point from an Amazon S3 bucket
that is configured as a site to a complex log tree.

• 6. Multi-value routing policy

• Multi-value routing policy helps return multiple values, e.g. IP addresses for the web
servers, in response to DNS quarries.
• Multi-value routing also helps check the heath of each resources, so only the value for
healthy resources are returned.
• 7. IP-addresses
• IP-based routing policy allows you to create a set of classes inter-domain routing (CIDR)
blocks that represent the client IP network ranges and map those CIDR blocks to
locations.
• These sets of CIDR blocks that are mapped to sets of locations are referred to as a CIDR
collection.