Which solution will give the application the ability to resolve the internal domain names?
Launch EC2 instances in the VPC. On the EC2 instances, deploy a custom DNS forwarder that forwards all DNS requests to the on-premises DNS server. Create an Amazon Route 53 private hosted zone that uses the EC2 instances for name servers.
Create an Amazon Route 53 Resolver outbound endpoint. Configure the outbound endpoint to forward DNS queries against the on-premises domain to the on-premises DNS server.
Set up two AWS Direct Connect connections between the AWS environment and the on-premises network. Set up a link aggregation group (LAG) that includes the two connections. Change the VPC resolver address to point to the on-premises DNS server.
Create an Amazon Route 53 public hosted zone for the on-premises domain. Configure the network ACLs to forward DNS requests against the on-premises domain to the Route 53 public hosted zone.
Explanations:
This option involves creating a custom DNS forwarder on EC2 instances, which is unnecessary. The correct solution should directly use AWS Route 53 Resolver with an outbound endpoint for DNS forwarding, rather than requiring EC2 instances and a private hosted zone.
Creating an Amazon Route 53 Resolver outbound endpoint is the appropriate solution. It enables the VPC to forward DNS queries to the on-premises DNS server, resolving domain names for internal resources in the on-premises network.
While AWS Direct Connect could improve connectivity, setting up multiple connections and changing the VPC resolver address does not address DNS resolution directly. The proper approach is using Route 53 Resolver to forward DNS queries.
A public hosted zone is not suitable for internal, on-premises domain resolution. Route 53 private hosted zones are required for internal DNS resolution, and forwarding DNS queries should be handled by an outbound endpoint, not a public hosted zone.