Resolve internal.example.com to a private IP in a VPC.
Do not publish the name to internet users.
Which configuration is most appropriate?
Associate a Route 53 private hosted zone with the VPC.
Detailed explanation
An S3 bucket name is not a Route 53 private hosted zone.
An S3 bucket name is not a Route 53 private hosted zone.
A public zone can expose an internal name and address to the internet.
A public zone can expose an internal name and address to the internet.
Only associated VPCs can resolve records in the private hosted zone.
Only associated VPCs can resolve records in the private hosted zone.
CloudFront is not a VPC-only DNS zone.
CloudFront is not a VPC-only DNS zone.
Check official documentation
Compare the following points with the official documentation.
Route 53 private hosted zonesの公式説明を確認する。
What to confirm
パブリックホストゾーンとプライベートホストゾーンを区別できる。
Key points
- Private hosted zone
- VPC association
- Internal DNS
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Visibility boundary
Private zones keep internal names and addresses out of public DNS.
Zone versus service
Route 53 hosts the record; the VPC supplies the resolver context.