Question

A company runs applications in a VPC that must resolve DNS records hosted on their on-premises Active Directory DNS servers (domain corp.internal), which are reachable over an existing AWS Direct Connect connection. Currently, EC2 instances in the VPC can resolve public domains and internal AWS resources but fail to resolve any corp.internal hostnames. A CloudOps engineer must enable resolution of corp.internal names from the VPC with the least operational overhead. What should the engineer configure?

Accepted Answer

Create a Route 53 Resolver outbound endpoint and a forwarding rule for corp.internal that targets the on-premises DNS server IPs, then associate the rule with the VPC.

Answer

Create a Route 53 Resolver inbound endpoint in the VPC and point the on-premises DNS servers to it as a conditional forwarder.

Answer

Create a Route 53 private hosted zone named corp.internal, associate it with the VPC, and manually add all on-premises records.

Answer

Deploy custom DNS forwarder EC2 instances in the VPC and update the DHCP options set to use their private IPs as the domain name servers.