If there is no default location configured in your geolocation routing setup, the DNS response returns NOERROR for the rcode field and there is no result in the ANSWER section. To correct this, add a default location in your geolocation routing setup.

2.    Use the Route 53 Test record set from the Checking Tool to determine which resource records are returned for a specific request. For more information, see

Using the Checking Tool to See How Amazon Route 53 Responds to DNS Queries.

3.    Route 53 supports the edns-client-subnet extension of EDNS0.The recursor or local name server appends edns-client-subnet to the DNS query to make a DNS lookup on the client's source IP subnet.

If this data isn't passed with the request, Route 53 uses the source IP address of the DNS resolver to approximate the location of the client and responds to geolocation queries with the DNS record for the resolver's location. If the EDNS

data isn't passed to Route 53 and the client is using a geographically diverse recursive name server, this would result in a suboptimal location serving the incorrect resource record to the DNS query.

To fix this, change the recursive DNS server that supports edns-client-subnet, perform the DNS resolution, and then share the output. If the recursive DNS server doesn't support the EDNS client subnet, try using one that does; for example, Google DNS, OpenDNS, and Amazon DNS server. For EC2-Classic

, the Amazon DNS server is located at 172.16.0.23. For EC2-VPC, the Amazon DNS server is located at the base of your VPC network range plus two.

4.    Check the client's DNS resolver to verify that it is geographically close their location. Route 53 uses resolver-identity.cloudfront.net to reflex the IP address where the DNS query came from. To collect IP addresses of resolvers, use a command to run every minute or schedule a cron job. For example, use one of the following: