Privacy Protection You can elect to hide your WHOIS information from the public so when a WHOIS query is made, the registrar information (Amazon Web Services) is returned and not your personal data. If you do not hide your personal data, you will most likely get a fair amount of spam in your inbox. WHOIS […]

Route 53 Failover Once all of the application-related tasks have been completed for the backup location, Route 53 needs to be configured with health checking, as shown in Figure 2.24. This allows for Route 53 to continuously check that the primary location is up, and should it stop responding to the checks, it will be […]

Using Route 53 Resolver Endpoints in Hybrid and AWS Architectures Resolvers in a VPC can be configured as either inbound, outbound, or both. Inbound allows queries from your internal DNS deployment to the DNS server in your VPC. Outbound enables VPC DNS queries to your on-premise DNS, and both enable queries in both directions. When […]

Multi-Region Route 53 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 […]

Route 53 Application Recovery Controller Application availability can be increased by using the Application Recovery Controller, which is a feature of Route 53 that monitors your endpoints and is used to determine if they have availability and are ready for recovery. You can use the routing control and readiness checking to manage failover using DNS […]

Route 53 Service Integrations There are many hooks and integrations between the many AWS service offerings. Since Route 53 is a very fundamental networking service that is used extensively within AWS to route traffic, there are many features added to Route 53 to integrate features and make configurations easier for the customer. Amazon does not […]

Weighted Routing Weighted routing is based on the round-robin policy but adds a weighted feature to affect how the load gets distributed. Multiple hosts with different IP addresses all serve the same content. Each host will then have a weight assigned to it between 0 and 255. If they are all set to the value of […]

Latency-Based Routing To enhance response times, a latency-based routing policy can be used. Route 53 will test the response times in the background of all the configured endpoints for a domain name. Route 53 determines the quickest response time between the origin and destination. This is the best destination value that is returned in the DNS […]

Traffic Routing Policies Routing policies are a Route 53 extension to DNS that allows you to customize query responses to affect how your content gets delivered. Routing policies shape the traffic based on our requirements in a number of different use cases. We can send all traffic to a single site, give multiple responses to […]

Resolvers DNS resolvers are at the heart of DNS functionality. Resolvers, also known as recursive resolvers, receive queries that contain the hostname and reply with the IP address of that hostname, as shown in Figure 2.7. The Route 53 Resolver acts as a bridge between your on-premise DNS infrastructure and the AWS VPC. Route 53 […]