ANS-C01 Question 307
Single answerYour company is hosting a hybrid architecture where on-premises systems need to resolve domain names of AWS-hosted resources using Route 53. You configure an Amazon Route 53 Resolver outbound endpoint in your VPC. However, the on-premises systems are unable to resolve the domain names of private hosted zones in Route 53. What additional step should you take to resolve this issue?
- A
Create an Amazon Route 53 Resolver inbound endpoint and associate it with the on-premises DNS server.
- B
Configure a Route 53 Resolver rule to forward queries for private hosted zones to the outbound endpoint.
- C
Enable DNS resolution for the VPC in the VPC settings.
- D
Associate the private hosted zones with the VPC where the outbound endpoint is configured.
Show answer and explanation
Correct answer: D
Explanation
In this scenario, private hosted zones in Route 53 are only resolvable from VPCs they are associated with. Even though an outbound endpoint is configured, the private hosted zones must be explicitly associated with the VPC where the outbound endpoint resides. This ensures that DNS queries to the private hosted zones are correctly resolved.
- A. Incorrect.
Creating an inbound endpoint is not necessary in this scenario since the requirement is for on-premises systems to resolve AWS private hosted zone names via the outbound endpoint.
- B. Incorrect.
Resolver rules are used to forward DNS queries to external DNS servers, not for resolving private hosted zone names. This does not apply here.
- C. Incorrect.
While enabling DNS resolution in the VPC settings is important for general DNS functionality within the VPC, it does not solve the specific issue of associating private hosted zones with the VPC.
- D. Correct.
Private hosted zones must be explicitly associated with the VPCs where they are to be resolved. Without this association, the private hosted zones cannot be queried, even with an outbound endpoint in place.