ANS-C01 · Question #101
You use a VPN to extend your corporate network into a VPC. Instances in the VPC are able to resolve resource records in an Amazon Route 53 private hosted zone. Your on-premises DNS server is…
The correct answer is A. Create a proxy resolver within the VPC. Point the on-premises forwarder to the proxy resolver. Here is a link that provides some detailed explanations on resolving DNS queries between VPCs and your network: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html Note that proxy resolver simply passes all requests to upstream DNS server and returns
Question
You use a VPN to extend your corporate network into a VPC. Instances in the VPC are able to resolve resource records in an Amazon Route 53 private hosted zone. Your on-premises DNS server is configured with a forwarder to the VPC DNS server IP address. On-premises users are unable to resolve names in the private hosted zone, although instances in a peered VPC can. What should you do to provide on-premises users with access to the private hosted zone?
Options
- ACreate a proxy resolver within the VPC. Point the on-premises forwarder to the proxy resolver.
- BModify the network access control list on the VPC to allow DNS queries from on-premises
- CConfigure the on-premises server as a secondary DNS for the private zone. Update the NS
- DUpdate the on-premises forwarders with the four name servers assigned to the private hosted
How the community answered
(20 responses)- A70% (14)
- B20% (4)
- C5% (1)
- D5% (1)
Explanation
Here is a link that provides some detailed explanations on resolving DNS queries between VPCs and your network: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html Note that proxy resolver simply passes all requests to upstream DNS server and returns
Topics
Community Discussion
No community discussion yet for this question.