Route 53 Flashcards
Global Domain Name System (DNS) web service that routes traffic to various targets with a single database
Route 53
Container for DNS records, and these records contain information about how you want to route traffic for a specific domain
Zones
indicates which DNS server is authoritative for that domain (i.e. which server contains the actual DNS records)
Nameserver Records
Record that maps host onto a IPv4 address
A record
Record that maps host onto a IPv6 address
AAAA record
Record that maps host to host
CNAME record
Indicates how email messages should be routed in accordance with the Simple Mail Transfer Protocol (SMTP, the standard protocol for all email)
MX records
Lets a domain administrator enter text into the Domain Name System (DNS) and prove ownership
TXT Records
Server setting that tells a cache how long to store DNS records before refreshing the search to get an answer again from a nameserver
TTL
Name Servers for the Hosted Zone
NS
Contains records that specify how to route traffic on the Internet (public domain names)
Public Hosted Zones
contain records that specify how you route traffic within one or more VPCs
Private Hosted Zones
Less traffic on Route 53, with possibly outdated record
High TTL
More traffic on Route 53, records are outdated for less
time and easy to change
Low TTL
Points a hostname to an AWS Resource
Alias
Can you set the TTL of Alias records?
No
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.
Failover Routing
Define how Route 53 responds to DNS queries
Routing Policies
Routing policy to configure Amazon Route 53 to route traffic to a single
resource
Simple 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
Weighted Policy
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 policy
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.
Geolocation Policy
Monitor the health and performance of your web applications, web servers, and other resources
Health-Check
Routing lets Amazon Route 53 (using traffic flow) 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
Routing is based on clients’ IP addresses
IP-based routing
Routing traffic to multiple resources
Multi-Value routing
