Implementing a Least Complex Solution for DNS Server Setup

Correct Answer - A.

Route 53 Resolver can be set up easily with low cost to forward DNS queries between on-premises & VPC.

In the above case, since DNS servers at on-premises locations need to be used for servers deployed in VPC, a Route 53 Resolver outbound endpoint needs to be set up with forwarding rules.

This outbound endpoint is not required to be created for each VPC, but a single endpoint can be shared between multiple VPCs.

There is no management overhead with this outbound endpoint, as once it's set up, you just need to manage forwarding rules.

Option B is incorrect as Inbound endpoints can be used to forward queries from on-premises into VPC.Option C is incorrect as configuring DNS forwarders on all instances will require additional admin work.

Option D is incorrect as implementing Zonal Forwarders is complex & will incur a higher cost than Router 53 Resolver Outbound endpoint.

For more information on using AWS Route 53 Resolver, refer to the following URL.

https://d1.awsstatic.com/whitepapers/hybrid-cloud-dns-options-for-vpc.pdf

The scenario described involves a global airlines company using hybrid connectivity for high availability application servers in both on-premises and VPC environments. Two VPCs, VPC A and VPC B, have been created across three availability zones for deploying multiple servers. The IT team is planning to set up a new DNS server at on-premises locations and servers in both VPC A and VPC B will need to forward queries to the new DNS server. The IT Head is looking to implement the least complex solution which can be implemented with ease, with the least management overhead and low cost.

There are four options provided in the answers, which are as follows:

A. Configure Route 53 Resolver with an outbound endpoint in VPC A and forwarding rules shared with VPC.

B. Configure Route 53 Resolver with an inbound endpoint in VPC A and forwarding rules shared with VPC.

C. Configure Distributed forwarders on each instance within VPN A and VPC B, which would forward queries to on-premises DNS servers.

D. Configure Zonal forwarders on multiple instances within VPN A and VPC B, which would forward queries to on-premises DNS servers.

Let's explore each option in more detail to see which one is the best fit for the requirement of the global airlines company.

Option A: Configure Route 53 Resolver with an outbound endpoint in VPC A and forwarding rules shared with VPC.

Route 53 Resolver is a service provided by AWS that allows inbound and outbound DNS resolution between VPCs and on-premises networks. With this option, an outbound endpoint would be created in VPC A, and the forwarding rules would be shared with VPC B. This option would enable the servers in both VPC A and VPC B to forward queries to the new DNS server.

However, this option may not be the least complex solution, as it requires the creation of an outbound endpoint and the sharing of forwarding rules. Additionally, there may be management overhead involved in managing the forwarding rules.

Option B: Configure Route 53 Resolver with an inbound endpoint in VPC A and forwarding rules shared with VPC.

Similar to option A, this option involves using Route 53 Resolver to forward queries to the new DNS server. However, in this option, an inbound endpoint would be created in VPC A, and the forwarding rules would be shared with VPC B. This option would enable the servers in both VPC A and VPC B to forward queries to the new DNS server.

This option may be less complex than option A, as it does not require the creation of an outbound endpoint. However, there may still be management overhead involved in managing the forwarding rules.

Option C: Configure Distributed forwarders on each instance within VPN A and VPC B, which would forward queries to on-premises DNS servers.

This option involves configuring distributed forwarders on each instance within VPC A and VPC B. These forwarders would forward queries to the new DNS server. This option may be the least complex solution, as it does not require the use of Route 53 Resolver, and there are no forwarding rules to manage.

However, there may be a higher management overhead involved in configuring and managing the distributed forwarders on each instance.

Option D: Configure Zonal forwarders on multiple instances within VPN A and VPC B, which would forward queries to on-premises DNS servers.

This option involves configuring zonal forwarders on multiple instances within VPC A and VPC B. These forwarders would forward queries to the new DNS server. This option may be less complex than option C, as it does not require the configuration of distributed forwarders on each instance.

However, there may still be a management overhead involved in configuring and managing the zonal forwarders on