Route 53

 Route 53





Introduction - 
  • Route 53 is the highly available and scalable domain name system provided by AWS
  • Global service
  • AWS manage authoritative (customer can update the DNS record
  • Also domain registrar
  • Only AWS service which 100% availability SLA
  • Affected by client DNS caching (not suitable for blue/green deployment if the client caches DNS queries
  • It is recommended to use DNS names or URLs instead of IPs whenever possible

DNS (Domain Name Service) - 
  • Domain Name System is an internet service that translate the domain name into IP address
  • Ex. - www.Amazon.com     (.com - Top level domain )    ( Amazon - Domain name )

Hosted Zone - 
  • A container for DNS records that define how to route traffic to its domain and its subdomain
  • Hosted zone is queried to get IP from hostname
  • There are two types of hosted zone
  1.  Public hosted zone - 
  • Resolves public domain name
  • Can be queried by anyone on the internet 
  1. Private hosted zone - 
  • Resloves private domain name 
  • Can be only queried from within the VPC

Record Types -
  • A - Maps the domain name to the IPv4 address of the server hosting the domain
  • AAAA - Maps the domain name to the IPv6 address of the server hosting the domain
  • Cname(canonical name) - Maps an alias domain name to the canonical domain name ,Used for  creating aliases for to other domains 
  • MX (Mail Exchange) - Specifies the mail server responsible for recieving email messages on behalf of domain 
  • NS(Name Server) - Specifies the name server for the domain, indicating which server are authoratative for the domain
  • SOA(Start of Authority) - Contains administrative information about the domain including the primary name server, the email of the domain administrator and various timers
 
Routing policies - 
  • Simple routing policy - Allows you to associate the single resourse record set with a route 53 domain name. This is useful when you have a single resource that performs a given function for your domain,such as your web server



  • Weighted routing policy - Allows you to associate multiple resource record set with a route 53 domain name and specify the weight for each record set. Route 53 uses the weight to determine how to distribute traffic among the record sets



  • Latency based routing policy - Allows you to route traffic based on lowest network latency for your end user. You can create latency records for multiple resources and route 53 will route the traffic to the resources with the lowest latency fot the end user



  • Failover routing policy - Allows you to configure active-passive failover configuration. You can create a primary school record set that recieves all traffic under normal condition and secondary record set that recieves the traffic only when primary set is unhealthy                    
      

 
  • Geo location routing policy - Allows you to route traffic based on the geographic location of your users. You can create geolocation records for different geographic location and specify the resource to which traffic should be routed for each location





  • That's all for Route 53 guys please email if you have any corrections, additions, queries or to discuss something about the above points. 
  • EMAIL - mahajanrohit759@gmail.com


 

Comments

Popular posts from this blog

AWS Instance Store

AWS Identity and Access Management

Elastic Block Storage (EBS)