EC2 instances in a VPC must resolve corp.example.com with an on-premises DNS server.
Use an existing Direct Connect or VPN path.
Which configuration is most appropriate?
Use a Route 53 Resolver outbound endpoint and forwarding rule for the corporate domain.
Detailed explanation
A public zone is not a private forwarding path for internal names.
A public zone is not a private forwarding path for internal names.
An S3 policy does not forward DNS queries.
An S3 policy does not forward DNS queries.
CloudFront is not an on-premises DNS forwarding service.
CloudFront is not an on-premises DNS forwarding service.
The rule forwards matching domain queries to the on-premises DNS server.
The rule forwards matching domain queries to the on-premises DNS server.
Check official documentation
Compare the following points with the official documentation.
Route 53 Resolver outbound endpoints and forwarding rulesの公式説明を確認する。
What to confirm
パブリックDNS、private hosted zone、Resolver forwardingを区別できる。
Key points
- Resolver outbound endpoint
- Forwarding rule
- On-premises DNS
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Selective forwarding
A rule can keep AWS names local while sending corporate names to the appropriate server.
Name resolution path
DNS forwarding requires both the endpoint and network reachability to the target resolvers.