description AWS Route 53 Resolver Endpoints Overview
DNS resolution failure is a common DR blind spot. Route 53 Resolver Endpoints allow you to manage DNS resolution across multiple VPCs and on-premises networks seamlessly. For DR, you can configure health checks and weighted routing policies to automatically direct traffic to the active region's endpoints, ensuring that clients always resolve the correct, operational IP address, even after a failover event.
help AWS Route 53 Resolver Endpoints FAQ
What is the difference between an inbound and outbound Route 53 Resolver endpoint?
An inbound endpoint lets DNS resolvers outside AWS query names that Route 53 Resolver can resolve inside a VPC. An outbound endpoint sends selected VPC queries to on-premises or other external DNS servers through forwarding rules.
How does Route 53 Resolver connect an AWS VPC to on-premises DNS?
A common hybrid design sends on-premises queries for AWS private names to an inbound endpoint and sends selected VPC queries to on-premises DNS through an outbound endpoint. The network path normally uses AWS Direct Connect or a VPN, and security groups must allow DNS traffic.
Can Resolver endpoints provide disaster-recovery DNS by themselves?
Resolver endpoints handle query forwarding and resolution, but they do not by themselves replace application failover logic. Route 53 health checks and routing policies such as weighted or failover routing may be used for public DNS, while private-service recovery needs its own design.
explore Explore More
Similar to AWS Route 53 Resolver Endpoints
See all arrow_forward
Reviews & Comments
Write a Review
Be the first to review
Share your thoughts with the community and help others make better decisions.
