Question

A company runs an on-premises data center connected to AWS via Direct Connect. Internal applications hosted on-premises need to resolve records in a private hosted zone named 'internal.example.com' that is associated with a VPC in the company's AWS account. Currently, on-premises servers can reach VPC resources over Direct Connect but cannot resolve the private hosted zone names. Which solution allows on-premises systems to resolve the AWS private hosted zone records with minimal operational overhead?

Accepted Answer

Create a Route 53 Resolver inbound endpoint in the VPC and configure on-premises DNS servers to forward queries for internal.example.com to the endpoint's IP addresses.

Answer

Create a Route 53 Resolver outbound endpoint in the VPC and add a forwarding rule pointing to the on-premises DNS servers.

Answer

Enable DNS hostnames and DNS resolution on the VPC and point on-premises servers to the VPC's default DNS resolver at the .2 address over Direct Connect.

Answer

Create a public hosted zone for example.com and add the internal records so they can be resolved from anywhere, including on-premises.