- Newest
- Most votes
- Most comments
Hi alansilver
Thank you for reaching out :)
To make the resolution of the Route 53 entries resolve for your computers that are connected to the VPC via AWS vpn, you can integrate DNS resolution between Resolver and DNS resolvers on your network by configuring forwarding rules.
You create Resolver inbound and/or outbound endpoints in your VPC. These endpoints provide a path for inbound or outbound queries:
Inbound endpoint: DNS resolvers on your network can forward DNS queries to Route 53 Resolver via this endpoint. This allows your DNS resolvers to easily resolve domain names for AWS resources such as EC2 instances or records in a Route 53 private hosted zone. For more information:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html#resolver-overview-forward-network-to-vpc
Outbound endpoint: Resolver conditionally forwards queries to resolvers on your network via this endpoint
To forward selected queries, you create Resolver rules that specify the domain names for the DNS queries that you want to forward (such as example.com), and the IP addresses of the DNS resolvers on your network that you want to forward the queries to. If a query matches multiple rules (example.com, acme.example.com), Resolver chooses the rule with the most specific match (acme.example.com) and forwards the query to the IP addresses that you specified in that rule. For more information:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html#resolver-overview-forward-vpc-to-network
Like Amazon VPC, Resolver is regional. In each region where you have VPCs, you can choose whether to forward queries from your VPCs to your network (outbound queries), from your network to your VPCs (inbound queries), or both.
The below link is a step-by-step guide on getting started with Route 53 Resolver:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver-getting-started.html
I hope this helps!
Relevant content
- asked 3 years ago
- Accepted Answerasked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago