Connect VPC to On-Premises DNS

Connect VPC to On-Premises DNS

Prev Question Next Question

Question

Your company currently has a VPC defined as 10.0.0.0/16

Subnets are defined in this VPC, along with Instances created in the subnet.

You need to ensure that resources in the VPC can resolve your on-premises DNS resources.

How can you achieve this? Choose 2 answers from the options given below.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Answer - A and B.

Here you can create your own EC2 Instance which will act as the DNS server.

The VPC can then use the DHCP Options which points to this EC2 Instance as the DNS resolver.

Option C is incorrect because the DHCP options set is tagged with the VPC and not the subnet.

Option D is incorrect because the private hosted zone should be used with routing requests in the VPC.For more information on DNS in a VPC, please refer to the below URL.

https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-dns.html

To allow resources in the VPC to resolve your on-premises DNS resources, you need to follow these steps:

  1. Create an EC2 Instance in your VPC which will act as the DNS server: You can create a new EC2 instance and install DNS software on it or use an existing EC2 instance that already has DNS software installed. This DNS server will be responsible for resolving DNS queries for resources in your VPC and forwarding them to your on-premises DNS servers.

  2. Create a private hosted zone in Route53: After creating the EC2 instance, you need to create a private hosted zone in Amazon Route 53. A private hosted zone is a container for DNS records that you can manage using the Route 53 API or console. You can use private hosted zones to route traffic between resources in your VPC and on-premises resources.

  3. Configure DHCP Options for your VPC to point to the EC2 Instance: To ensure that all resources in your VPC use the new DNS server, you need to configure DHCP options for your VPC to point to the IP address of the EC2 instance you created in step 1. DHCP (Dynamic Host Configuration Protocol) is a network protocol used to automatically assign IP addresses and other network configuration parameters to devices on a network.

  4. Configure DHCP Options for your Subnet to point to the EC2 Instance: You also need to configure DHCP options for each subnet in your VPC to point to the IP address of the EC2 instance. This ensures that resources created in each subnet use the new DNS server.

By following the above steps, you can ensure that resources in your VPC can resolve your on-premises DNS resources.