ANS-C01 Question 208
Single answerAn organization has deployed a hybrid infrastructure where applications are spread across their on-premises data center and AWS. The on-premises network uses a private DNS server for internal resolution, and they have created a private hosted zone in Amazon Route 53 for AWS-based resources. They want to ensure that their on-premises applications can resolve DNS queries for AWS-hosted resources in the private hosted zone without modifying their existing DNS server settings. What is the best solution to achieve this?
- A
Use an AWS Lambda function to forward DNS queries from the on-premises network to the Route 53 Resolver.
- B
Configure Route 53 Resolver inbound endpoints and update the on-premises DNS server to forward queries to these endpoints.
- C
Create a public hosted zone in Route 53 for the AWS resources and use it instead of the private hosted zone.
- D
Set up AWS Systems Manager to synchronize DNS records between the on-premises DNS server and the Route 53 private hosted zone.
Show answer and explanation
Correct answer: B
Explanation
To enable DNS resolution for AWS private hosted zones from an on-premises network, you can use Route 53 Resolver inbound endpoints. These endpoints allow the on-premises DNS server to forward queries to the private hosted zone in AWS, providing seamless resolution without modifying existing DNS server settings. This is the most efficient and AWS-recommended solution for hybrid DNS configurations.
- A. Incorrect.
This option is incorrect because AWS Lambda is not designed for DNS query forwarding or resolution. While it could theoretically be set up to handle DNS queries, it would be overly complex, inefficient, and not a recommended approach.
- B. Correct.
This option is correct because Route 53 Resolver inbound endpoints allow on-premises DNS servers to forward DNS queries to AWS for resolution in private hosted zones. This solution integrates seamlessly and does not require changes to the existing DNS server settings beyond setting up a forwarding rule.
- C. Incorrect.
This option is incorrect because creating a public hosted zone would expose internal DNS records to the internet, which is a security risk and not appropriate for private resources. Furthermore, this does not achieve the desired outcome of private resolution.
- D. Incorrect.
This option is incorrect because AWS Systems Manager is not designed to synchronize DNS records between on-premises DNS servers and Route 53 private hosted zones. This would require custom scripts and is not a native or recommended approach.