Your company has the requirement of connecting its on-premises location to an AWS VPC. The on-premises servers should have the capabilities of resolving custom DNS domain names in the VPC. The Instances in the VPC need to have the ability to resolve the DNS names of the on-premises servers. How can you achieve this?

Answer options:

A.Setup a DNS forwarder in your VPC. Ensure the DNS forwarder points to the Amazon DNS resolver for the VPC. Also, ensure the forwarder is configured with the on-premises DNS server. Change the Option Set for the VPC for the IP address of the DNS forwarder. Configure a DNS forwarder in the On-premises location.
B.Setup a DNS forwarder in your VPC. Ensure the DNS forwarder points to the Name server for the Route 53 hosted zone. Also, ensure the forwarder is configured with the on-premises DNS server. Change the Option Set for the VPC for the IP address of the DNS forwarder. Configure a DNS forwarder in the On-premises location.
C.Setup a DNS forwarder in your VPC. Ensure the DNS forwarder points to the IP address of the On-premises DNS server. Change the Option Set for the VPC for the IP address of the DNS forwarder. Configure a DNS forwarder in the On-premises location.
D.SetupDNS forwarder in your VPC. Ensure the DNS forwarder points to the IP address of the VPN tunnel. Change the Option Set for the VPC for the IP address of the DNS forwarder. Configure a DNS forwarder in the On-premises location.

Answer – A
Option B is incorrect because the DNS forwarder needs to point to the DNS resolver for the VPC and not the Name servers.
Option C is incorrect because the DNS forwarder should also point to the DNS resolver for the VPC.Option D is incorrect because the DNS forwarder should not point to the VPN tunnel IP address.
An example of this is given in the AWS Documentation.
For more information on this example, please refer to the below URL
https://aws.amazon.com/blogs/security/how-to-set-up-dns-resolution-between-on-premises-networks-and-aws-by-using-unbound/