Geolocation routing in private hosted zones - Amazon Route 53
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Geolocation routing in private hosted zones

For private hosted zones, Route 53 responds to DNS queries based on the Amazon Web Services Region of the VPC that the query originated from. For the list of Amazon Web Services Regions, see Regions and zones in the Amazon EC2 user guide.

If the DNS query originates from an on-premises part of a hybrid network, it will be considered as having originated from the Amazon Web Services Region that the VPC is located in.

If you include health checks, you can create default records for:

  • IP addresses that aren't mapped to geographic locations.

  • DNS queries that come from locations that you haven't created geolocation records for.

If the geolocation record for the DNS query's region is unhealthy, the default record will be returned (if it is healthy).

In the example configuration in the following figure, DNS queries coming from an us-east-1 Amazon Web Services Region (Virginia) will be routed to the 1.1.1.1 endpoint.

A screenshot that shows a geolocation record for a private hosted zone.