Route 53 (associate) Flashcards
What is DNS?
- It’s a Domain Name system which translate the human friendly host names into the machine IP addresses & is the backbone of the internet
- DNS uses hierarchical naming structure:
1. .com
2. example.com
3. www.example.com
What are the different DNS Terminologies?
- Domain registrar: Amazon route 53, godaddy, etc
- DNS record: A, AAAA, CNAME. NS…
- Zone file: contains DNS records
- Name server: resolved DNS queries (authoritative or non-authoritative)
- Top level domain (TLD): .com, .us, .in, .gov, .org
- Second level domain (SLD): Amazon.com, google.com
https://api.www.example.com.
(. at the end is the root)
(. after example and everything with it is the TLD)
(. After www and everything after is the SLD)
(. After api and everything after is sub domain)
(api and everything after is the FQDN (fully qualified domain name)
(http is the protocol)
And the whole thing is called the URL
__________ is a highly availabl, scalable, fully managed & authoritative DNS which means the customer can update the DNS record
Amazon Route 53
The route 53 records will contain what?
- Domain/subdomain name (ex. Example.com)
- Record type (ex. A or AAAA)
- Value (12.34.56.78)
- Routing Policy (how route 53 responds to queries)
- TTL(amount of time the record cached at DNS resolvers)
What are the different route 53 record types?
- A: maps a host name to IPv4
- AAA: maps a host name to IPv6
- CNAME: maps a host name to another host name (the target is a domain name that must have an A or AAA record & can’t create CNAME record for the top node of a DNS namespace)(ex. Can create one for example.com but can create one for www.example.com)
- NS: name servers for the hosted zone (control how traffic is routed for a domain)
____________ is a container for record that define how to route traffic to a domain and it’s subdomains
Route 53 - Hosted Zones
What are the two types of hosted zones?
- Public hosted zones: contains record that specify how to route traffic on the internet (public domain name)
- Private hosted zones: contain record that specify how you route traffic within one or more VPC
- Pay 0.50 per month per hosted zone (not free)
_________ means time to live, how a client has to cache results
Route 53 Record TTL
- High TTL (ex 24hrs)
- less traffic on route 53 & possibly outdated record - Low TTL (ex 60secs)
- More traffic on Route 53
- Record are outdated less time and easy to change records
- The TTL is mandatory for every DNS record except for Alias Record
What is the difference between CNAME & Alias ?
CNAME:
- Points a host name to any other host name ( app.mydomain.com => Blabla.anything.I’m)
- Only for non root domain (aka.something.mydomain.com)
Alias:
- Points a host name to an AWS resource (app.mydomain.com=> Blabla.Amazonas.com)
- Works for root domain & non root domain (aka.mydomain.com)
- Free of charge
- Native health check
- Maps to a host name to an AWS resource
- An extension to DNS functionality
- Can be used for the top node of a DNS namespace
- Alias record is always of type A/AAAA for AWS resources (IPv4 / IPv6)
- Can’t set the TTL (set automatically by route 53)
What are the targets for Alias records?
- ELB
- Cloudfront distributions
-API Gateway - Elastic beanstalks environments
- S3 websites
- VPC interface endpoints
- Global accelerator accelerator
- Route 53 record in the same hosted zone
- You can’t set an ALIAS record for an EC2 DNS name
_________ define how route 53 responds to DNS queries
Route 53 routing policy
What are the different routing policies for route 53?
- Simple
- Weighted
- Failover
- Latency based
- Geolocation
- Multi- Value answer
- Geoproximity
What are some features of simple routine policy?
- Typically 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 Alia’s enabled, specify only one AWS resource
- Can’t be associated with health checks
What are some features of weighted routine policy?
- Control the % of the request that go to each specific resource
- Assign each record a relative weight:
- Traffic (%) = weight for a specific record/ sum of all the weights for all records - DNS records must have the same name & type
- Can be associated with health checks
- Use cases: load balancing, between regions, testing new applications versions
- Assign a weight of 0 to a record to stop spending traffic to a resource
- If all record have weight of 0, then, all record will be returned equally
What are some features of latency -based routine policy?
- Redirects to the resource that has the least latency is to us
- Super helpful when latency for users is priority
- Latency is based on traffic between users & AWS regions
- Germany user may be directed to the US (if that’s the lowest latency)
- Can be associated with health checks (has failover capability)