Route 53 Global DNS Flashcards

1
Q

R53 Hosted Zone

A

DNS Data base for a domain

what the DNS system references Authoritative for a domain

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is the resiliency of R53 ?

A

it’s Globally resilient with multiple DNS servers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What does Host Zones contain ?

A

Host DNS records

e.g. A, AAAA, MX NS and TXT

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

How many name servers are there per hosted zone ?

A

4 R53 name servers(NS) specific for the zone

accessible from public internet and VPC

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Private Hosted Zones

A

associated with VPC

only accessible in those VPCs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Split View or Split Horizon DNS

A

overlapping public and private for public and internal uses with the same Zone name

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Route 53 Health Checks

A

health checks are separate from, but are used by records

checks if an record is healthy or unhealthy

in most cases an unhealthy record is not returned in queries

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Some benefits of R53 health checks

A

endpoint, cloudWatch alarms, check of checks calculated

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

How often are checks by default

A

check every 30s (every 10s cost extra)

checks connection by TCP, HTTP/HTTPs with string matching

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

A records

A

maps a Name to an Ip address

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

CNAME records

A

maps a name to another name

e.i. www.catagram.io => catagram.io

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Limitation of Cnames

A

CNAME is invalid for naked/Apex domain

i.e. catagram.io

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Alias Record

A

maps a name to an AWS resource

can be used for both naked/apex and normal

no charge for Alias pointing at AWS resources

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Why user an Alias record over a CName record

A

Many AWS services us a DNS name (ELB)

Name : catatgram.io ==> ELB would be invalid

for AWS services the default is an Alias

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Route53 Simple Routing

A

simple routing doesn’t support health checks - all values are returned for a record when queried

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What case would simple routing be best ?

A

use simple routing when you want to route requests towards one service such as a web server

17
Q

Route53 Weighted Routing

A

Each record is return based on it’s record weight vs total weight

if a chosen record is unhealthy, the process of selection is repeated until a healthy record is chosen

18
Q

What does it mean when a record has a ‘0’ in Weighted Routing ?

A

A ‘0’ weight means a record is never returned unless all are ‘0’ then all are considered

19
Q

Route53 Failover Routing

A

if the target of the health check is ‘Healthy’ the primary record is used

if the target of the health check is unhealthy any queries return the secondary record of the same name

20
Q

When would you user weighted Routed ?

A

simple load balancing or testing new software versions

21
Q

What is the user case for Failover Routing ?

A

user when you want to configure active passive failover

a common architecture is to use failover for a ‘out of band’ failure / maintenance page for a service (e.g EC2/S3 )

22
Q

Route53 Multi Value Routing

A

Muli Value Routing supports Multiple records with the same name

Up to 8 ‘healthy ’ records are returned. if more exit 8 are randomly selected

each record has it’s own health check if a not healthy the record won’t be returned

23
Q

When would you user multi value routing ?

A

Multi value routing improves the availability

it is not a replacement for load balancing

24
Q

Route53 Latency-Based Routing

A

AWS maintains a database of latency between the users general location and the regions tagged in records

Latency-based Routing supports one record with the same name in each AWS region

The record returned is the one which offers the lowest estimated latency and is healthy

25
Q

Route53 Geolocation Routing

A

R53 checks for records 1) in the state, 2) in the country, 3) the continent and 4)(optionally) default specified by you

it returns the most specific record or ‘No Answer’

26
Q

When would you use Geolocation Routing ?

A

can be used for regional restriction, language specific content or load balancing across regional endpoints

27
Q

Route53 Geoproximity Routing

A

Routing is distance based including a bias

‘+’ or ‘-’ vais can be added to rules. ‘+’ increases a region size and decreases neighbouring regions

28
Q

Route 53 Registry only

A

The domain is register via R53 but the NS records for the domain are set to external hosted Name servers.

Not to common because most of Route53 benefit comes from hosting.

29
Q

Route53 Hosting Only

A

Creates a R53 public Hosted zone for the domain Pass the allocated NS details to the registrar

30
Q

Route 53 Both

A

Route 53 handles both registry and Hosting