A company’s network engineer is designing a hybrid DNS solution for an AWS Cloud workload. Individual teams want to manage their own DNS hostnames…

This combination creates a standard and scalable hybrid DNS architecture using managed AWS services, minimizing overhead.
- Amazon Route 53 private hosted zones (E) allow development teams to manage their own DNS records for their applications within their VPCs.
- An Amazon Route 53 Resolver outbound endpoint (C) enables resources within the VPC to resolve hostnames in the on-premises network by forwarding queries to the on-premises DNS servers.
- An Amazon Route 53 Resolver inbound endpoint (A) allows the on-premises network to resolve hostnames within AWS VPCs (defined in the private hosted zones) by forwarding queries to the Route 53 Resolver.

B. Modifying the DHCP options set is a client-side configuration within the VPC. The core logic for bidirectional resolution is handled by Resolver endpoints and rules, not the DHCP options.
D. Creating DNS proxy servers on EC2 instances adds significant management overhead, which contradicts the requirement to minimize it. Route 53 Resolver is the managed service that replaces this pattern.
F. Amazon Route 53 does not support DNS zone transfers (AXFR/IXFR) for private hosted zones. Resolution is handled via forwarding rules and endpoints.

1. AWS Documentation, "Resolving DNS queries between VPCs and your network," Amazon Route 53 Developer Guide. This document details the architecture using inbound and outbound endpoints for hybrid DNS resolution.

2. AWS Documentation, "Working with private hosted zones," Amazon Route 53 Developer Guide. This section explains how private hosted zones are used for DNS within one or more VPCs.

3. AWS Whitepaper, "Hybrid Cloud DNS Solutions for Amazon VPC," (aws-hybrid-cloud-dns-vpc.pdf). This paper outlines architectural patterns, including the recommended use of Route 53 Resolver endpoints (see Figure 5, page 9).