A company is using custom DNS servers that run BIND for name resolution in its VPCs. The VPCs are deployed across multiple AWS accounts that are part of the same organization in AWS Organizations. All the VPCs are connected to a transit gateway. The BIND servers are running in a central VPC and are configured to forward all queries for an on-premises DNS domain to DNS servers that are hosted in an on-premises data center. To ensure that all the VPCs use the custom DNS servers, a network engineer has configured a VPC DHCP options set in all the VPCs that specifies the custom DNS servers to be used as domain name servers. Multiple development teams in the company want to use Amazon Elastic File System (Amazon EFS). A development team has created a new EFSle system but cannot mount the file system to one of its Amazon EC2 instances. The network engineer discovers that the EC2 instance cannotresolve the IP address for the EFS mount point fs-33444567d.efs.us-east-1.amazonaws.com. The network engineer needs to implement a solution so that development teams throughout the organization can mount EFS file systems. Which combination of steps will meet these requirements? (Choose two.)
Show Answer & Explanation
Correct Answers: A. Configure the BIND DNS servers in the central VPC to forward queries for efs.us-east-1.amazonaws.com to the Amazon provided DNS server (169.254.169.253).; D. Create an Amazon Route 53 Resolver rule to forward queries for the on-premises domain to the on-premises DNS servers. Share the rule with the organization by using AWS Resource Access Manager (AWS RAM). Associate the rule with all the VPCs.
Option A: The BIND servers need to forward queries for AWS service domains (like EFS endpoints) to the Amazon-provided DNS (169.254.169.253) so they can resolve AWS service endpoints. This allows the custom DNS to handle on-premises queries while delegating AWS service resolution to AWS DNS. Option D: Route 53 Resolver rules can forward queries for the on-premises domain to on-premises DNS servers. Sharing the rule via AWS RAM and associating it with all VPCs ensures consistent DNS resolution across the organization. Options B and C are incorrect because they suggest replacing the BIND servers entirely, which contradicts the requirement to keep using custom DNS for on-premises resolution. Option E creates unnecessary manual DNS record management.