A global logistics provider is establishing a hybrid DNS architecture. On-premises servers must resolve DNS names in an AWS Private Hosted Zone (PHZ) named corp.logistics.aws associated with AWS VPCs. Conversely, EC2 instances inside AWS VPCs must resolve DNS names for on-premises servers under the domain onprem.logistics.local. A centralized network VPC contains the hybrid connectivity interfaces. Which configuration steps must the solutions architect perform to establish two-way DNS resolution? (Select TWO.)
- Configure the on-premises DNS servers to forward queries for corp.logistics.aws to the IP addresses of a Route 53 Resolver inbound endpoint created in the centralized VPC.Answer
- Create a Route 53 Resolver outbound endpoint in the centralized VPC, and create a forwarding rule for onprem.logistics.local targeting the on-premises DNS servers.Answer
- CShare the Private Hosted Zone corp.logistics.aws with the on-premises DNS servers using AWS Resource Access Manager (RAM).
- DConfigure a Route Table in the centralized VPC to route DNS queries for corp.logistics.aws directly to the Direct Connect Gateway (DXGW).
Answer
Configure the on-premises DNS servers to forward queries for corp.logistics.aws to the Route 53 Resolver inbound endpoint IPs, and create a Route 53 Resolver outbound endpoint with a forwarding rule for the on-premises domain.
Establishing two-way hybrid DNS resolution requires both an inbound endpoint and an outbound endpoint. The inbound resolver endpoint accepts queries forwarded from on-premises DNS servers for AWS-hosted domains. The outbound resolver endpoint, combined with a forwarding rule, directs AWS queries for on-premises domains to the on-premises DNS infrastructure.
Step-by-Step Solution
Key Concept
Hybrid DNS resolution requires Route 53 Resolver inbound endpoints for queries entering AWS, and outbound endpoints with forwarding rules for queries exiting AWS.