In this lab, you’ll use the three tools (Outbound Endpoint, Resolver Rules, and Inbound Endpoints) of Route 53 Resolver to set up a hybrid DNS for your AWS infrastructure and On-premises.
The AWS Managed Microsoft Active Directory service you created in the previous section will be used to simulate your DNS on-premise system. The following figure will show the architecture that you will continue to build on top of the infrastructure you deployed in the previous section:
Once done, you’ll understand how to set up a DNS hybrid between DNS hosted zones on your on-premises system and in AWS. In the exercise, we used the AWS Managed Microsoft AD DNS server to simulate the DNS on-premise system. To visualize integration with your actual on-premise environment, you need to specify IP addresses for your DNS on-premise servers instead of the AWS Managed Microsoft AD * IP addresses DNS*. To allow your DNS on-premise servers to resolve any AWS Private Zones hosted on Route 53, you would create DNS forwarding rules in the DNS system on- your premises. For DNS domains hosted on Route 53, forward to the IP address of the Inbound Endpoint.