Start preparing for your Next Exam | Use coupon – TOGETHER | Avail 30% discount

Understanding Route 53

  1. Home
  3. AWS Certified Advanced Networking Specialty Exam
  5. Understanding Route 53

Overview for Understanding Route 53

  • For understanding Route 53, you must understand it is an,
    • Authoritative
    • highly available
    • scalable
    • cloud DNS service by AWS
  • maximum of 50 domain names
  • compatible with IPv6
  • control and optimize Traffic flow by routing traffic to best location as per latency/geography/target health, etc.
  • Private DNS to manage private addresses, and resolution only if request from specific VPC.
  • DNS failover feature
    • monitors resource health
    • requests not routed to unhealthy resources
    • Used to create backup sites.
  • single record  can have multiple IPs
  • DNS chang propagates within 60 seconds by Route 53 depending on network conditions
  • Allows management of mappings between domain names and IP addresses (records)
  • replies to “queries” for translating domain names to IP address
  • routing on port 53
  • can register and manage new domains
  • It monitors health of applications using configuration
  • If health checks fail, it disables endpoint for time as per TTL
  • Use ELB for load balancing
  • Traffic Flow application
    • is a visual editor
    • Can create complex routing policies spanning multiple regions and environments.
  • ELBs operate on domain names only, and not on fixed IPv4 or IPv6 addresses.
  • Health checks and monitoring executes as per configuration for same.
    • No routing to unhealthy resources
    • unhealthy endpoint get disable till it becomes healthy
    • unhealthy is found as TTL  usually 60 seconds
    • ELBs can be used for load-balancing on target’s health
  • Can register and manage new domains with Route 53.
  • visual editor is provided, called Traffic Flow
    • create routing policies spanning multiple AZs and regions
  • Not possible to use an A Record to resolve to an ELB, use an Alias record
Hosted Zones
  • To manage multiple domain names and records.
  • Every hosted zone is created for second-level domain only
  • can in turn contain records and sub-domains for that second-level domain.
Aliases
  • Aliases can map to internal AWS resources, like ELB’s, CloudFront distributions, Elastic Beanstalk environments, and S3 buckets.
  • Unlike CNAMEs, Alias records exist only inside Route 53.
  • They are not visible to resolvers.
  • Alias of the zone apex can be created but not CNAME
  • Alias queries are free.

 

Get ready to qualify AWS Advanced Networking – Specialty Exam with hundreds of practice exam and expert guidance. Try Now!

 

Menu