Route 53 is a global AWS service and is not specific to any region. You can configure zone records that are hosted in any region or that are outside of the AWS cloud such as your own data center. Route 53 extensions allow Multi-Region failovers by enabling health checking.
Multi-Region latency-based routing is a Route 53 feature that directs users to the region hosting the service with the fastest response time or lowest latency. For example, if a user in Zurich requests a connection to www.tipofthehat.com, as we discussed earlier, Route 53 with latency-based routing enabled will check and see that Frankfurt has a response time of 125 milliseconds, for example, and Ireland is responding on average in 150 milliseconds. Given that Frankfurt has the lowest latency, Route 53 will reply to the Zurich user’s request with the IP address of the web server in Frankfurt. Geo-based directs use an AWS region based on their location, and weighted route-robin responds to DNS queries with a rotating list of IP addresses across the regions you define to evenly disperse the load between multiple regions. Route 53 DNS failover will direct all traffic to a primary region, and should that not respond to health checks, it begins replying with IP addresses for the backup region.
A public hosted zone is used in Route 53 to route traffic over the Internet for a specific domain such as tipofthehat.com and all of its subdomains such as dev.tipofthehat.com, test.tipofthehat.com, and prod.tipofthehat.com. Hosted zones are created when you register a domain in Route 53 or when you transfer an externally registered domain into AWS. A public hosted zone contains your defined instructions about how you direct traffic on the Internet to your domain by defining records. When a public zone is created, Route 53 will automatically create the name server (NS) and start of authority (SOA) records.
Private hosted zones are used to store records for your internal, non-Internet, hosts. Route 53 will respond to queries that are for resources running inside of your VPC. Every zone can support services and servers in multiple VPCs if the zone is associated with the VPC.
The private hosted zone is used strictly to route internally to your VPC and can connect to services such as ELB, an EC2 instance, or any service that has an IP address endpoint. Once the private hosted zone is created, then resource records can be added to define your endpoint records. For Internet-bound DNS queries, use the public hosted zone.
Acedexam Training Policies
Learning resources
Other resources
Our Training Providers
