AWS Certified SAA | 17 Apr 2019
- Route53 gets its name from port 53 of DNS server
- IPv4 space is 32 bit fields having over 4 billion different addresses.
- IPv6 solves the depletion issue and has as address space of 128 bits
- For each public hosted zone Route 53 automatically created NS record and SOA record (Start of Authority Record)
- NS Record - is used by Top Level Domain servers to direct traffic to the Content DNS server which contains the authoritative DNS records
- When creating a public hosted zone, Route 53 gives you NS records in different Top-Level Domains.
- The start of authority (SOA) record identifies the based DNS information about the domain.
- SOA record components
- NS that created the SOA record
- Email of the administrator
- The current version of the data file
- The default number of seconds for the time-to-live file on resource records
- Domain to IP request flow
- Top Level Domain
- NS Records
- The lower the TTL (time to live), the faster changes to DNS records take to propagate through the internet
- CNAME records can't be used for naked domain names (zone apex record). It must be either A record or an Alias
- Given a choice between Alias record and CNAME always choose an Alias record
- Common DNS Types
- SOA Records
- NS Records
- A Records
- MX Records
- PTR Records
- You can buy domain names directly with AWS
- It can take up to 3 days to register depending on the circumstances
- Routing Policies
- Simple Routing
You can only have one record with multiple IP addresses. If you specify multiple values in a record, Route 53 returns all values to the user in a random order.
Simple routing cannot be associated with a health check.
- Weighted Routing
Traffic can be split based on different weights assigned.
- Latency-based Routing
Allows you to route your traffic based on the lowest network latency for your end user.
- Failover Routing
- Active/passive set up
- Specifying primary and secondary records
- Health check is associated with the primary record
- Geolocation Routing
Lets you choose where your traffic will be sent based on the geographic location of your users.
- This is not a latency based routing - the routes are locked down based on geolocation.
- Geoproximity Routing (Traffic Flow Only)
Georproximity routing lets Route53 route traffic to your resources based on the geographic location of your users and your resources. You can optionally choose to route more traffic or less to a given resource by specifying a value, know as bias. A bias expands or shrinks the size of the geographic region from which traffic is routed to a resource. To use this you must use Route53 Traffic flow.
- Multivalue Answer Routing
Exactly the same as Simple Routing, however, allows you to use health checks on each record. Route53 will return values for healthy resources.
- Simple Routing
- Health Checks
- You can set health checks on individual record sets
- If a record set fails a health check it will be removed from Route53 until it passes the health check
- You can set SNS notifications to alert you if a health check is failed
- Health Checks can be created and associated with Route 53 records
- Route 53 is built using AWS's highly available and reliable infrastructure.
- Each Amazon Route 53 hosted zone is served by its own set of virtual DNS servers. They are assigned by the system when the hosted zone is created.
- Amazon Route 53 charges are based on actual usage of the service for Hosted Zones, Queries, Health Checks, and Domain Names.
- Access to Route53 can be controlled using IAM.
- You can configure Amazon Route 53 to log information about the queries that Amazon Route 53 receives including date-time stamp, domain name, query type, location etc. to CloudWatch Logs.
- Amazon Route53 uses anycast network - is a networking and routing technology that helps your end users' DNS queries get asnwered from the optimal Route53 location given network conditions.
- Route53 account is limited to a maximum of 500 hosted zones and 10,000 resource record sets per hosted zone and 50 domains.
- Multiple hosted zones can be created for domain.
- In addition to standard record types supported by Route53, alias records are supported, which is Route 53-specific extension to DNS. Alias can be used to map your entires to AWS Resources.
- Wildcard entries are supported.
- Zone apex can be mapped to AWS Resources by using alias records.
- Traffic Flow makes it easy for developers to create policies that route traffic based on constraints like: latency, endpoint health, multivalue; answers, weighted round robin, and geo. In addition to these, Traffic Flow also supports geoproximity based routing with traffic biasing.
- Traffic Policy is the set of rules that routes end users' request to one of the application's endpoints.
- Policy Record associates the traffic policy with the appropriate DNS name within an Amazon Route 53 hosted zone that you own.
- You are billed from Traffic Flow per Policy Record.
- Private DNS should be attached to a VPC
- Route53 Health checks could verify the expected content of the web server by using the "Enable String Matching" option.
- Amazon Route 53’s metric based health checks let you perform DNS failover based on any metric that is available within Amazon CloudWatch, including AWS-provided metrics and custom metrics from your own application.
- Domains registered are configured to renewal automatically. Route53 provides privacy protection at no additional charge.
- Route53 registers top-level domains through either Amazon Registar or Gandi.
- Route53 Resolver is a regional DNS service that provides recursive DNS lookups for names hosted in EC2 as well as public names on the internet.
- Route 53 is Authoritative and Recursive DNS. Authoritative DNS - contains the final answer to a DNS query. Recursive DNS - forwards the query directly to a specific recursive DNS server.