route 53

Question 1

what is route 53

Answer 1

Amazon Route 53 provides highly available and scalable Domain Name System (DNS), domain name registration, and health-checking web services.

Question 2

What can I do with Amazon Route 53?

Answer 2

• -create and manage public DNS records;
• -answers requests to translate specific domain names like into their corresponding IP addresses.
• -offers health checks to monitor the health and performance of your application as well as your web servers and other resources.

Question 3

CreateHostedZone API

Answer 3

create a hosted zone that can store DNS records for your domain. Upon creating the hosted zone, you receive four Route 53 name servers across four different Top-leveldomains(TLDs).

Question 4

domain vs hosted Zone?

Answer 4

domain is a general DNS concept like amazon.com
hosted zone is an Amazon Route 53 concept. is analogous to a trafitional DNS zone file; it represents a collection of records that can ne managed together, belonging to a single parent domain name. all resource records sets within a hosted zone must have the same suffix like www.aws.amazon.com, www.amazon.com.

Question 5

I have subscribed for Amazon Route 53 but when I try to use the service it says “The AWS Access Key ID needs a subscription for the service”

Answer 5

When you sign up for a new AWS service, it can take up to 24 hours in some cases to complete activation, during which time you cannot sign up for the service again.

Question 6

Does Amazon Route 53 use an anycast network?

Answer 6

Yes. Anycast is a networking and routing technology that helps your end users’ DNS queries get answered from the optimal Route 53 location given network conditions. As a result, your users get high availability and improved performance with Route 53.

Question 7

Amazon routed 53 limits

Answer 7

each route 53 account is limited to 500 hosted zones and 10,000 resources record sets per hosted zone.
50 domains,

Question 8

Can I create multiple hosted zones for the same domain name?

Answer 8

yes.

Question 9

Does Amazon Route 53 also provide website hosting?

Answer 9

No

Question 10

Which DNS record types does Amazon Route 53 support?

Answer 10

A (address record)
AAAA (IPv6 address record)
CNAME (canonical name record)
CAA (certification authority authorization)
MX (mail exchange record)
NAPTR (name authority pointer record)
NS (name server record)
PTR (pointer record)
SOA (start of authority record)
SPF (sender policy framework)
SRV (service locator)
TXT (text record)
Additionally, Amazon Route 53 offers ‘Alias’ records (an Amazon Route 53-specific virtual record).

Question 11

Does Amazon Route 53 support wildcard entries? If so, what record types support them?

Answer 11

Yes. all record types except for NS.

Question 12

What is the default TTL for the various record types and can I change these values?

Answer 12

Amazon Route 53 does not have a default TTL for any record type. You must always specify a TTL for each record so that caching DNS resolvers can cache your DNS records to the length of time specified through the TTL.

Question 13

Can I associate multiple IP addresses with a single record?

Answer 13

Yes. Associating multiple IP addresses with a single record is often used for balancing the load of geographically-distributed web servers. Amazon Route 53 allows you to list multiple IP addresses for an A record and responds to DNS requests with the list of all configured IP addresses.

Question 14

Does Amazon Route 53 support DNSSEC?

Answer 14

Amazon Route 53 does not support DNSSEC for DNS at this time. But Amazon Route 53 allows DNSSEC on domain registration.

Question 15

Does Amazon Route 53 support IPv6?

Answer 15

Yes. Amazon Route 53 supports both forward (AAAA) and reverse (PTR) IPv6 records.

Question 16

Does Amazon Route 53 support Weighted Round Robin (WRR)?

Answer 16

Yes. Weighted Round Robin allows you to assign weights to resource record sets in order to specify the frequency with which different responses are served.

Question 17

What is the difference between Latency Based Routing and Geo DNS?

Answer 17

Geo DNS bases routing decisions on the geographic location of the requests. In some cases, geography is a good proxy for latency; but there are certainly situations where it is not. LatencyBased Routing utilizes latency measurements between viewer networks and AWS datacenters. These measurements are used to determine which endpoint to direct users toward.

If your goal is to minimize end-user latency, we recommend using Latency Based Routing. If you have compliance, localization requirements, or other use cases that require stable routing from a specific geography to a specific endpoint, we recommend using Geo DNS.

Question 18

Can I create an Alias record pointing to a DNS name that is managed by a traffic policy?

Answer 18

No

Question 19

Is there a charge for traffic policies that don’t have a policy record?

Answer 19

No. We only charge for policy records; there is no charge for creating the traffic policy itself.

Question 20

Can I still use Private DNS if I’m not using VPC?

Answer 20

No. Route 53 Private DNS uses VPC to manage visibility and provide DNS resolution for private DNS hosted zones. To take advantage of Route 53 Private DNS, you must configure a VPC and migrate your resources into it.

Question 21

Can I use the same private Route 53 hosted zone for multiple VPCs?

Answer 21

Yes, you can associate multiple VPCs with a single hosted zone.

Question 22

What DNS record types can I associate with Route 53 health checks?

Answer 22

You can associate any record type supported by Route 53 except SOA and NS records.

Question 23

How many consecutive health check observations does an endpoint need to fail to be considered “failed”?

Answer 23

The default is a threshold of three health check observations: when an endpoint has failed three consecutive observations, Route 53 will consider it failed. However, Route 53 will continue to perform health check observations on the endpoint and will resume sending traffic to it once it passes three consecutive observations. You can change this threshold to any value between 1 and 10 observations.

Question 24

What is the interval between health check observations?

Answer 24

By default, health check observations are conducted at an interval of 30 seconds. You can optionally select a fast interval of 10 seconds between observations.

Question 25

Do HTTPS health checks validate the endpoint’s SSL certificate?

Answer 25

No, HTTPS health checks test whether it’s possible to connect with the endpoint over SSL and whether the endpoint returns a valid HTTP response code. However, they do not validate the SSL certificate returned by the endpoint.