A company hosts its main website at the zone apex (example.com). The website is served by regional Application Load Balancers (ALBs) located in the us-east-1 (United States), eu-west-1 (Europe), and ap-southeast-1 (Singapore) regions. The SysOps Administrator has configured Amazon Route 53 Geolocation routing records for the zone apex pointing to each regional ALB. However, users in South America and Africa report that they receive DNS resolution errors when trying to access the website, while users in the United States, Europe, and Singapore can access it successfully. Which configuration change should the SysOps Administrator make to resolve this issue?
- ACreate a CNAME record for example.com with a Geolocation routing policy set to 'Default' pointing to the public DNS name of the ALB in us-east-1.
- BChange the routing policy for the existing records from Geolocation to Failover, designating us-east-1 as the primary endpoint and eu-west-1 as the secondary endpoint.
- Create an Alias A record for example.com with a Geolocation routing policy set to 'Default' pointing to the ALB in us-east-1.Cevap
- DAdd a new record for example.com with a Failover routing policy, specifying the ALB in us-east-1 as the primary record without associating a Route 53 health check.
Cevap
Create an Alias A record for example.com with a Geolocation routing policy set to 'Default' pointing to the ALB in us-east-1.
The correct answer is to create an Alias A record for the zone apex pointing to the us-east-1 ALB with a Geolocation routing policy set to 'Default'. Geolocation routing requires a default record to handle queries from any location that is not explicitly defined in other records (such as South America and Africa in this scenario). Furthermore, because the target domain is at the zone apex (example.com), standard CNAME records cannot be used. An Alias A record successfully maps the zone apex to the ALB.
Adım Adım Çözüm
Anahtar Kavram
Route 53 Geolocation Routing Default Record and Zone Apex Alias Constraints