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 efficient hybrid DNS architecture using managed AWS services. Amazon Route 53 private hosted zones (E) allow development teams to manage their own DNS records within their VPCs. To enable bidirectional name resolution, an Amazon Route 53 Resolver inbound endpoint (A) is used to allow on-premises DNS servers to forward queries for the private zones to AWS. Conversely, a Resolver outbound endpoint (C), along with forwarding rules, enables the VPC's internal DNS resolver to forward queries for on-premises domains to the company's DNS servers. This solution leverages fully managed services, directly meeting the requirement to minimize management overhead.

B. Modifying the DHCP options set to a custom DNS server bypasses the integrated Route 53 Resolver, which is essential for this managed hybrid solution.

D. Creating DNS proxy servers on EC2 instances introduces significant operational overhead for patching, scaling, and availability, which contradicts the requirement to minimize management.

F. Amazon Route 53 does not support DNS zone transfers (AXFR/IXFR) for private hosted zones, making this an technically infeasible option for this scenario.

1. Amazon Route 53 Developer Guide: This guide details the components for hybrid DNS. It states, "To allow DNS queries to be forwarded from your network to Route 53 Resolver, you create a Resolver inbound endpoint... To forward DNS queries from your VPCs to your network, you create a Resolver outbound endpoint."

Source: AWS Documentation, Amazon Route 53 Developer Guide, Section: "Resolving DNS queries between VPCs and your network".

2. AWS Documentation on Private Hosted Zones: "You can use private hosted zones to manage custom domain names for your internal AWS resources without exposing the corresponding DNS data to the public internet." This directly supports the requirement for teams to manage their own internal hostnames.

Source: AWS Documentation, Amazon Route 53 Developer Guide, Section: "Working with private hosted zones".

3. AWS Whitepaper on Hybrid Cloud DNS: Architectures for hybrid DNS are detailed, specifying the use of Route 53 Resolver endpoints for conditional forwarding as the recommended, low-overhead pattern. It contrasts this with the higher-overhead model of managing DNS forwarders on EC2 instances.

Source: AWS Whitepapers, Hybrid Cloud DNS Solutions for Amazon VPC, Page 7-9, "Pattern 1: On-Premises DNS Is Authoritative".