A company has a multi-account architecture with a central networking account that hosts a Transit Gateway. Each workload account has VPCs attached to the Transit Gateway. The company wants to centrally manage DNS resolution across all VPCs using Route 53 Resolver. They create a Route 53 Resolver outbound endpoint in the networking account and associate it with the workload VPCs via RAM. However, workload accounts cannot resolve on-premises hostnames. What is the missing configuration?
Trap 1: Establish VPC peering between the workload VPCs and the networking…
VPC peering is not needed for DNS forwarding when Transit Gateway is used.
Trap 2: Create a Route 53 private hosted zone in the networking account and…
Private hosted zone resolves domain names to AWS resources, not forwarding to on-premises.
Trap 3: Create a Route 53 Resolver inbound endpoint in the networking…
Inbound endpoint is for on-premises to resolve AWS resources, not the other way.
- A
Establish VPC peering between the workload VPCs and the networking account VPC.
Why wrong: VPC peering is not needed for DNS forwarding when Transit Gateway is used.
- B
Create a Route 53 private hosted zone in the networking account and associate it with the workload VPCs.
Why wrong: Private hosted zone resolves domain names to AWS resources, not forwarding to on-premises.
- C
Create a Route 53 Resolver inbound endpoint in the networking account.
Why wrong: Inbound endpoint is for on-premises to resolve AWS resources, not the other way.
- D
Create a Route 53 Resolver rule in each workload account that forwards queries for the on-premises domain to the outbound endpoint.
Resolver rules determine how DNS queries are forwarded.