0% found this document useful (0 votes)
44 views20 pages

AWS Route 53 Guide for IT Professionals

AWS route S3 explained here easily
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
44 views20 pages

AWS Route 53 Guide for IT Professionals

AWS route S3 explained here easily
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

6)

67
16
93
By Bhupinder Rajput

46
,8
om
l.c
ai
gm
6@
59
ry
ha
ud
ha
ac
hn
ris
Route 53
(k
frj
N
0m
to
n gs
lo
be
F
PD
is
Th
Route 53

Th
is
PD
F
be
lo
n

gs
We can use Route-53 to register new domains, transfer existing domains,

to
0m
route traffic for our domains to our AWS and external resources and monitor

N
frj
(k
the health of our resources.

ris
hn
• DNS TCP port number is 53.This is the reason why amazon used the name

ac
ha
ud
Route 53.

ha
ry
59
6@
gm
ai
l.c

om
1.DNS Management

,8
Route-53

46

93
2.Traffic Management

16
67
6)
• 3.Availability Monitoring
Functions • 4.Domain Registration
2
Route 53 (Contd..)

Th
is
PD
F
be
lo
ngs
Route-53 performs three main functions :

to
0m

N
1.Register a domain.

frj
(k

ris
2.As a DNS, it routes internet traffic to the resources for our domain.

hn
ac
• 3.Check the health of our resources.

ha
ud
o

ha
Route-53 sends automated requests over the internet to a resource (can be a

ry
59
webserver) to verify that the server is, reachable functional or available.

6@
gm
o Also we can choose to receive notifications when a resource becomes

ai
l.c
om
unavailable and choose to route internet traffic away from unhealthy resources

,8
46
93
16
• We can use Route-53 for any combination of these functions :

67
6)
o EX : We can use Route-53 both to register our domain name and to route
internet traffic for the domain.
o Or we can use Route-53 to route internet traffic for a domain that we
registered with another domain register. 3
Route 53 (Contd..)

Th
is
PD
F
be
lo
ngs
• When we register a domain with Route-53,the service automatically makes

to
0m
itself the DNS service for the domain by doing the following :

N
frj
(k
ris
1. It creates a hosted zone that has the same name as our domain.

hn
ac
ha
2.It assigns a set of four name servers to the hosted zone, unique to the account.

ud
ha
ry
o When someone uses a browser to access our website, these name servers

59
6@
gm
inform the browser where to find our resources, such as a web server or an

ai
l.c
Amazon S3 bucket.

om
,8
o It gets the name servers from the hosted zone and adds them to the domain.

46
93
16
67
6)
4
Route 53 (Contd..)

Th
is
PD
F
be
lo
ngs
to
0m
AWS Supports

N
frj
(k
• 1.Generic Top level. Domains.com,.org,.net etc.

ris
hn
• 2.Geographic Top Level Domains......in,.us,.me etc.

ac
ha
ud
ha
Registering a domain with Route-53

ry
59
6@
• We can register a domain with route-53 if the TLD is included on the supported TLD list.

gm
ai
• If the TLD is not included, we can't register the domain with route-53.

l.c
om
,8
46
Using Route-53 as our Service

93
16
67
• We can use Route-53 as the DNS service for any domain, even if the TLD for the domain

6)
is not included on the supported TLD list.
• Note : Each amazon Route-53 account is limited to a maximum of 500 hosted zones and
10,000 resource record sets per hosted zone. We can increase this limit by requesting to
AWS.
5
Route 53 (Contd..)

Th
is
PD
F
be
lo
ngs
to
Steps to configure Route-53

0m
N
frj
(k
ris
hn
• 1.We need to register a domain, this can be route-

ac
ha
ud
53,or another DNS registrar, but then we connect

ha
ry
59
our domain name in that registrar to route-53.

6@
gm
• 2.Create hosted zone on route-53 (if we

ai
l.c
om
purchased domain from registrar other than route-

,8
46
93
53), this is done automatically if we registered our

16
67
6)
domain using route-53.
• Inside the hosted zone, we need to create record
sets.
6
Route 53 (Contd..)

Th
is
PD
F
be
lo
ngs
Delegate to Route-53

to
0m
• This step connects everything and make it works.

N
frj
• Connect the domain name to the route-53 hosted zone. This is called delegation.

(k
ris
• Update our domain registrar with the correct name servers for our route-53 hosted zone.

hn
ac
• No other customer hosted zone will share this delegation set with us.

ha
• Doing this means route-53 DNS service will be serving DNS traffic for the domain of the hosted zone.

ud
ha
• If we registered our domain with a diff registrar, we need to configure the route-53 NS's list in our registrar

ry
59
DNS database for our domain.

6@
gm
When we are using another domain provider and we did all the changes

ai
l.c
om
• When we migrate from one DNS provider to another, For an existing domain this change can take upto 48

,8
46
hours to be effective.

93
• This is because name server DNS records are typically cached across the DNS system globally on the

16
67
internet for upto 48 hours (TTL) periods.

6)
Transferring a Domain to Route-53

• We can transfer a domain to route-53 if the TLD is included on the Amazon supported TLD list.
• If the TLD is not included, we cant transfer the domain to Route-53.
• For most TLD, we need to get authorization code from the current registrar to transfer a domain.
7
Route 53 (Contd..)

Th
is
PD
F
be
lo
ngs
Route-53 Hosted Zone

to
0m
• A route 53 hosted zone is a collection of records for a specified domain.

N
frj
• We create a hosted zone for a domain and then we create records to tell the domain name system how we

(k
ris
want traffic to be routed for that domain.

hn
ac
• Basically a hosted zone is a container that holds information about how we want to route traffic for domain

ha
and its sub domains.

ud
• We can create public (internet) hosted zone or private (internal) hosted zone.

ha
ry
• For each public hosted zone that we create amazon route 53 automatically creates name server (ns) record

59
6@
and a start of authority (SOA) record. Don't change these records.

gm
• Route 53 automatically creates a name server (ns) record with the same name as our hosted zone.

ai
• It list the four name servers that are authoritative name servers for our hosted zone.

l.c
om
• Do not add, change or delete name servers in this record.

,8
• When we create a hosted zone, amazon route-53 automatically creates a name server (ns) records and a

46
93
start of authority record (SOA) for the zone.

16
• The ns record identifies the four name servers that we give to our registrar or our DNS service so that DNS

67
6)
queries are routed to route53 name servers.
• By default route-53 assigns a unique set of four name servers (known collectively as a delegation set).
• Ex : ns-1337 awsdns-39.com
• ns-895 awsdns-47.net
• ns-428 awsdns-53.org
• ns-1597 awsdns-07.co.uk
8
Route 53 (Contd..)

Th
is
PD
F
be
lo
ngs
Route 53 as our Authoritative DNS

to
0m
•Once we update the route 53 NS settings with our domain registrar to include the route 53

N
frj
name server, route 53 will be responsible to respond to DNS queries for the hosted Zone.

(k
ris
•This is true whether we do have a functioning website or not.

hn
ac
•Route53 will respond with information about the hosted zone whenever someone types the

ha
associated domain name in a web browser.

ud
ha
•We can create more than one hosted zone with the same name and add diff records to each hosted

ry
59
zone.

6@
•Route 53 assigns four name servers to every hosted zone.

gm
•The name servers are diff for each of them.

ai
l.c
•When we update our registrars name server records, be careful to use the route 53 name servers

om
,8
for the correct hosted zone the one that contains the records that we want route 53 to use when

46
responding to queries for our domain.

93
16
•Route 53 never returns values for records in other hosted zone that have the same name

67
6)
Route 53 Hosted zone default entries

•Inside the hosted zone by default we have two entries :


•NS Entry : Contains the unique sets of name servers for this hosted zone.
•SOA entry : Contains information about the hosted zone . 9
Route 53 (Contd..)

Th
is
PD
F
be
lo
ngs
DNS Record Types

to
0m
N
•If we are currently using another DNS service and we want to migrate to Amazon Route 53 :

frj
(k
•Start by creating Hosted Zone.

ris
hn
•Route 53 automatically assigns the delegation sets, the four name servers to our hosted zone.

ac
ha
•To ensure that the DNS routes queries for our domain to the route 53 name servers.

ud
•Update our registrar's or our DNS servers NS records for the domain to replace the current Name

ha
ry
servers with the names of the four Route 53 name servers for our hosted zone.

59
6@
•The method that we use to update the NS records depends on which registrar or DNS service we

gm
are using.

ai
l.c
•Some registrar only allow us to specify name servers using IP addresses they dont allow us to

om
specify fully qualified domain names.

,8
46
•If our registrar requires using Ip addresses, we can get the IP addresses for our name servers

93
using the dig utility (for mac and Linux) and nslookup( for windows).

16
67
6)
Transferring a domain between accounts within AWS

•Transferring a domain to a diff AWS account :


•If we registered a domain with one AWS account and we want to transfer the domain to another
AWS account, we can do so by contacting the AWS support center and Requesting the transfer.
10
Route 53 (Contd..)

Th
is
PD
F
be
lo
ngs
Migrating a hosted zone to a diff AWS account

to
0m
•If we are using Route53 as the DNS service for the domain, route53 does not transfer the hosted

N
frj
zone when we transfer a domain to a diff AWS account.

(k
ris
•If domain registration is associated with one account and the corresponding hosted zone is

hn
associated with another account, neither domain registration nor DNS functionality is affected.

ac
ha
•The only effect is that we will need to sign into the route 53 console using one account to see the

ud
ha
domain and signin using the other account to see the hosted zone.

ry
59
6@
Supported DNS Record Types by Route 53

gm
ai
l.c
•1.A record : Address Record maps domain names to IP Address (32 bit IPv4 Address),

om
,8
www.techguftugu.com in A 5.5.5.5

46
•2.AAAA Record : IPv6 address record maps domain name to an IPv6 address (128 bit IPv6

93
16
address so the name AAAA [32bits*4]).

67
•3.CNAME Record : Canonical name record maps an alias to a hostname. Web in CNAME

6)
techguftugu.com.
•4.NS record : Name server Record used for delegating zone to a nameserver. techguftugu.com in
NS ns1.techguftugu.com.
•5.SOA Record : Start of Authority Record.
•6.MX record : Mail exchange defines where to deliver mail
for user@domain name.techguftugu.com in MX 10 mail.techguftugu.com. 11
Supported DNS Record Types by Route 53

Th
is
PD
F
be
lo
ngs
NS record

to
0m
• It defines which name server is an authoritative to a particular zone or domain name and point us to other DNS servers.

N
• A/AAAA are called host records, like business cards.

frj
(k
• CNAME is an alternative records, or an alias for another record.

ris
• Helpful in redirection or if we want to hide details about our actual servers from the user.

hn
ac
ha
SOA Record

ud
ha
• Every single zone has one and only SOA resource record at the beginning of the zone.

ry
59
• It is not an actual record, it includes the following info :

6@
• Who the owner is (email for the domain).

gm
• The authoritative server.

ai
• The serial number which is incremental with changes to the zone data.

l.c
• The refreshing time/cycle info and the time to live (TTL).

om
,8
46
93
CNAME Record

16
67
• A CNAME value element is the same format as a domain name.

6)
• The DNS protocol does not allow us to create a CNAME record for the top node of a DNS namespace, also known as the zone apex (or
root domain).
• For EX : if we register the DNS name techguftugu.com, the zone apex is techguftugu.com and we cannot create a CNAME
for techguftugu.com.
• However we can create CNAME records for WWW.techguftugu.com,support.techguftugu.com and so on.
• In addition, if we create a CNAME record for a subdomain we cannot create any other record for that Subdomain.
• EX: If we create a CNAME for www.techguftugu.com we cannot create any other records for which the value of the name
field is www.techguftugu.com . 12
Supported DNS Record Types by Route 53

Th
is
PD
F
be
lo
ngs
to
CNAME Record

0m
N
frj
(k
• A CNAME value element is the same format as a domain name.

ris
hn
• The DNS protocol does not allow us to create a CNAME record for the

ac
ha
ud
top node of a DNS namespace, also known as the zone apex (or root

ha
ry
domain).

59
6@
• For EX : if we register the DNS name techguftugu.com, the zone apex is

gm
ai
techguftugu.com and we cannot create a CNAME for techguftugu.com.

l.c
om
• However we can create CNAME records

,8
46
for WWW.techguftugu.com,support.techguftugu.com and so on.

93
16
• In addition, if we create a CNAME record for a subdomain we cannot

67
6)
create any other record for that Subdomain.
• EX: If we create a CNAME for www.techguftugu.com we cannot create
any other records for which the value of the name
field is www.techguftugu.com .
13
Routing Policy

Th
is
PD
F
be
lo
ngs
Routing Policies

to
0m
N
frj
• When we create a record, we choose a routing policy, which determines

(k
ris
how amazon route 53 respond to Queries.

hn
ac
• Simple, Failover, Geo Location, Latency, Geo Proximity, Weighted and

ha
ud
ha
Multi-Level Routing Policies.

ry
59
6@
gm
Failover Routing Policy

ai
l.c
om
,8
• Failover routing lets us route trafiic to a resource when the resource is

46
93
16
healthy if the main resource is not healthy, then route traffic to diff

67
6)
resource.
• The primary and secondary records can route traffic to anything from an
amazon S3 buccket that is configured as a website to a complex tree of
records.
• Failover routing policy is applicable for public hosted zone only. 14
Geolocation Routing

Th
is
PD
F
be
lo
n

gs
It lets us choose the resources that serves our traffic based on the geographic

to
0m
location of our users i.e. the location that DNS queries originate from.

N
frj
• Ex : We may have presence in Europe and Asia and we want users in the Asia to

(k
ris
hn
be served in the Asia and those in Europe to be served by servers in Europe.

ac
ha
ud
• Benefits :

ha
ry
59
6@
o We can localize our content and present some or all of our website in the language

gm
of our users.

ai
l.c
om
o We can also use geolocation routing to restrict distribution of content to only the

,8
46
locations in which we have distribution rights.

93
16
o We can specify geographic locations by continent, by country or by state in the US.

67
6)
o If we create separate records for overlapping geographic regions for ex : one record
for North America and one for Canada-priority goes to the smallest geographic
region (Canada).
o Geolocation works by mapping IP address to location. However some IP address 15
are not mapped to geographic location.
Latency Based Routing

Th
is
PD
F
be
lo
• If our application is hosted in multiple amazon ec2 regions, we can improve performance for our

ngs
users by serving their request from the amazon ec2 region that provides the lowest latency.

to
0m
• To use this routing we need to create latency records for our resources in multiple ec2 regions.

N
frj
(k
ris
• When amazon route 53 receives a DNS query for our domain or subdomain

hn
ac
o It determines which amazon ec2 region we have created latency record for.

ha
ud
o Determine which regions gives lowest latency to users.

ha
ry
59
o Then select a latency record for that region

6@
gm
• Ex : Suppose we have ELB in US-East and in Asia pacific (Mumbai) region.

ai
l.c

om
We created a latency record for each load balancer.

,8

46
Here's what happened when a user in London enters the name of our domain in browser.

93

16
DNS routes the request to a route 53 name server.

67

6)
Route 53 refers to its data on latency between London and the Mumbai region and between
London and N.Virginia.
• If latency is lower between London and N.verginia, route 53 respond to the query with the IP address
for the N.verginia LB.
16
Weighted Routing Policy

Th
is
PD
F
be
lo
• It lets us associate multiple resources with a single domain name or subdomain name

ngs
to
and choose how much traffic is routed to each resource.

0m
N
• This can be useful for a variety of purposes, including load balancer and testing new

frj
(k
ris
versions of software.

hn
ac

ha
Weights can assign any number from 1 to 255.

ud
ha
• Weighted routing policy can be applied when there are multiple resource that

ry
59
6@
performs the same function. Ex : Webserver serving the same website.

gm

ai
To configure weighted routing, we create records that have the same name and type

l.c
om
for each of our resources.

,8
46

93
Amazon route 53 sends traffic to a resource based on weight that we assign to the

16
67
record as a proportion of the total weight for all records in the group.

6)
• Ex : Suppose for www.tg.com has three resource record sets with weights of 1(20%)
,1(20%) and 3(60%). Sum =5.
• On average, route 53 select each of the first two resources record set one-fifth of the
time and returns the third resource record set three-fifth of the time. 17
Geo Proximity Routing Policy

Th
is
PD
F
be
lo
ngs
• Use when we want to route traffic based on the location of our

to
0m
N
resources and optionally, shift traffic from resources in one location to

frj
(k
ris
resources in another.

hn
ac
ha
• We can also optionally choose to route more traffic or less to a given

ud
ha
resource by specifying a value, known as a ‘bias’. A bias expand or

ry
59
6@
shrinks the size of the geographic region from which traffic is routed

gm
ai
l.c
to a resource.

om
,8
46
93
16
67
6)
18
Multivalued Answer Routing Policy

Th
is
PD
F
be
lo
• Use this, when we want route 53 to respond to DNS queries with upto eight healthy record

ngs
to
selected at random.

0m

N
This lets us configure amazon route 53 to return multiple values, such as IP addresses for

frj
(k
ris
our webservers in response to DNS queries. We can specify multiple values for almost

hn
ac
any record, but multivalue answer routing also lets us check, the health of each resource,

ha
ud
so route 53 returns only values for healthy resources. Its not a substitute for our load

ha
ry
balancer but the ability to return multiple health checkable IP addresses is a way to use

59
6@
DNS to improve availability and load balancing.

gm
ai
l.c
Name Type​ Value TTl Set I.D H,C

om
,8
(HealthCheck)​

46
93
www.tg.com​ A​ 192.0.2.2​ 60​ web1​ A​

16
67
6)
www.tg.com​ A​ 195.50.100. 60​ web2​ B​
1​
www.tg.com​ A​ 200.1.1.1​ 60​ web3​ C​
19
www.tg.com​ A​ 192.0.3.3​ 60​ web4​ D​
Th
is
PD
Thanks!

F
be
lo
ngs
to
0m
N
frj
(k
ris
Any questions?

hn
ac
ha
ud
ha
You can find me at:

ry
59
6@
gm
ai
@TechnicalGuftgu

l.c
om
,8
46
technicalguftgu99@gmail.com

93
16
67
6)
20

You might also like