Chp 10: Route 53

Question 1

What is Route 53

Answer 1

• DNS
• also a Domain registrar
• only AWS service that is able to provide 100% availability
• how you route traffic for a domain

Question 2

Route 53 supports what record types?

Answer 2

• A: maps ip4 to hostname
• AAAA: maps ipv6 to hostname
• CNAME: maps a hostname to another hostname
• NS: name servers for the hosted zone

Question 3

What is a Route 53 Hosted Zone

Answer 3

• a container for records that define how to route traffic to a domain + its subdomain

Question 4

Route 53 – Records to TTL

Answer 4

1. high ttl

2. low ttl

Question 5

describe high ttl

Answer 5

• • less traffic on route 53

- - possibly outdated records

Question 6

describe low TTL

Answer 6

• • more traffic on route 53
• • records are outdated for less time
• • easy to change new records

Question 7

What is an alias?

Answer 7

• • points a hostname to an aws resource
• • work for non root and root domain
• • free of charge
• • native health checks

Question 8

Route 53 alias records

Answer 8

• automatically recognizes changes in the resource IP addresses
• can be used for top node of a namespace
• always of type A/AAAA
• TTL cant be set

Question 9

Route 53 routing policies

Answer 9

• defines how route 53 responds to DNS queries

Question 10

What are the routing policy types

Answer 10

1. simple
2. weighted
3. failover
4. geolocation
5. multi-value answer
6. geoproximity

Question 11

Routing Policy: Simple

Answer 11

• Route traffic to a single resource
• can specify multiple values in the same record
• if multiple values are returned, a random one is chosen by the client
• when alias is enabled, specify only one aws resource
• cant be associated with health checks

Question 12

Routing Policy: Weighted

Answer 12

• controls the % of teh requests that go to each resource
• assign each record a relative weight. weights dont need to add up to 100
• dns must have the same name + type
• can be associated with health checks
• use case: load balancing between regions, testing new app version
• assign a record a weight of - to stop sending resources
• if all records have a weight of 0, then all records will be returned equally

Question 13

Routing Policy: Latency-based

Answer 13

• redirect resources that has the least latency
• latency is based on traffic between users and AWS region
• can be associated with health check

Question 14

Routing Policy: Health Checks ( failover)

Answer 14

• HTTP health checks are only for public resource
• health check: automated DNS failover
• health checks are integrated with cw metrics

Question 15

Routing Policy: Geolocation

Answer 15

• routing based on user location
• specify location by continent, country of by us state
  should create a default record in case there is no match
• use case: website localization, load balancing
• can be associated with health checks

Question 16

Routing Policy: Geoproximity

Answer 16

• route traffic to your resource based on geographic location of users and resources
• ability to shift more traffic to resources based on the defined bias
• to change the size of the geographic region, specify bias values
• resources can be aws or non-aws
• you must use route 53 traffic flow to use this feature

Question 17

Routing Policy : Multivalue

Answer 17

• use wen routing traffic to multiple resources
• route 53 return multiple value/resources
• can be associated with health checks
• up to 8healthy records are returned for each multi-value query
• multi-value is not a substitute for having an ELB

Question 18

Domain registrar vs dns service

Answer 18

you can purchase a domain registrar and use route 53 to manage it