Route 53 - Global DNS Flashcards
Is Route 53 globally resilient
Yes
container that holds information about how you want to route traffic on the internet for a specific domain, records stored in them are publicly resolvable
Public Hosted Zones
container that holds information about how you want Amazon Route 53 to respond to DNS queries for a domain and its subdomains within one or more VPCs
Private Hosted Zone
Maps a NAME to an IPv4 or IPv6 address
“A” record (IPv4) “AAAA” record (IPv6)
Maps a NAME to another NAME
CNAME record
record at the top node of a DNS namespace, also known as the zone apex that maps a NAME to an AWS resource
Alias Record
lets you configure standard DNS records, with no special Route 53 routing such as weighted or latency. Resolves your DNS to a resource as is
Simple Routing
monitor the health and performance of your web applications, web servers, and other resources
Health Check
Are Health Checks seperate from records?
Yes but they are used by records
Default health check interval
30 seconds
health checker evaluates the health of the endpoint based on two values
response time and failure threshold
Whether the endpoint responds to a number of consecutive health checks that you specify
Failure threshold
HTTP and HTTPS, TCP, and HTTP and HTTPS with string matching are how health checks determine if an endpoint is healthy or unhealthy
True
Health checks can monitor an endpoint, other health checks or monitor CloudWatch alarms
True
Routing policy lets you route traffic to a resource when the resource is healthy or to a different resource when the first resource is unhealthy. You can specify two DNS records with the same DNS name and have them point to two different targets
Failover Routing
Routing policy to configure Amazon Route 53 to return multiple values, such as IP addresses for your web servers, in response to DNS queries to improve availability
Multi value routing
routing policy that lets you associate multiple resources with a single domain name and choose how much traffic is routed to each resource based on the the weights you assign for each target. The greater the weight, the greater the traffic portion it receives
Weighted routing
routing policy for when you have resources in multiple AWS Regions and you want to route traffic to the region that provides the fastest performance
latency-based routing
Routing policy lets you choose the resources that serve your traffic based on the geographic location of your users, meaning the location that DNS queries originate from. Allows you to restrict distribution of content to only the locations in which you have specified
Geolocation routing
routing lets Amazon Route 53 route traffic to your resources based on the geographic location of your users and your resources and, optionally, shift traffic from resources in one location to resources in another
Geoproximity routing
When positive, Route 53 treats the source of a DNS query and the resource that you specify in a geoproximity record (such as an EC2 instance in an AWS Region) as if they were closer together than they really are
Bias
