Exploring AWS !!
Day 15:
Route53 — Routing Policies
Public Hosted Zone contains information about how the traffic on internet should be routed for a domain.
NS record set: The authoritative name servers for domain name.
SOA (State of Authority) record set: Contains base DNS information about domain.
[ns-2048.awsdns-64.net.hostmaster.example.com 1 7200 900 1209600 86400]
ns-2048.awsdns-64.net: Host that created SOA record.
hostmaster.example.com: email address of admin with ‘@’ being replaced by ‘.’
86400: minimum TTL
Private Hosted Zone contains information how to route the traffic for a domain within one or more VPCs.
Note: to use private hosted zones, following VPC setting have to be set to TRUE:
- enable DNS-Hostnames
- enable DNS-Support
Simple Routing Policy: A single server performing desired operation
Failover Routing Policy: Two servers performing Active-Passive routing
Weighted Routing Policy: associates multiple resources with same DNS name and type. Each record is given a weight and set ID.
Latency Routing Policy: If an application is hosted on EC2 instance in multiple regions, user latency can be reduced by serving requests from regions where latency is lowest. We’ve to create a latency resource record set for EC2 instance in each region that hosts the application. Latency record sets can be created for both EC2 and ELB instance. Latency over internet can be changed over time due to changes in routing or something else.
Geo-location Routing Policy: can be used to send traffic to resources based on geographical location to users. Example, all queries from Europe can be routed to IP addresses. It works by wrapping ID address irrespective of regions to locations.
Top comments (0)