Route 53 Resolver Infographic
Networking & Content Delivery

Route 53 Resolver

Seamlessly bridging DNS resolution between your On-Premises data centers and AWS Virtual Private Clouds (VPCs).

The Core Components

Inbound Endpoints

“Let On-Prem talk to AWS”

Allows on-premises DNS servers to forward queries to Route 53 Resolver via IP addresses.

Outbound Endpoints

“Let AWS talk to On-Prem”

Enables Resolver to forward DNS queries from your VPC to your on-premises DNS infrastructure.

Forwarding Rules

“The Traffic Controller”

Defines which domain names (e.g., corp.internal) should be sent to which on-premises DNS servers.

Direct Connect/VPN

“The Physical Bridge”

The underlying private network connection that allows endpoints to communicate securely.

How the Hybrid DNS Flow Works

A visual guide to bidirectional name resolution

ON-PREMISES Local DNS Server 10.0.0.53 AWS VPC EC2 INSTANCES ROUTE 53 RESOLVER Inbound Endpoint Outbound Endpoint Query: aws.internal Query: corp.internal
01

The Inbound Path

On-premises applications query your local DNS. If the domain is within AWS, the local DNS forwards the request to the Route 53 Inbound Endpoint IP.

02

The Outbound Path

EC2 instances query the VPC Resolver. If the domain matches a Forwarding Rule, the Resolver sends the query through the Outbound Endpoint to On-Prem.

Security First

Integrates with AWS IAM and CloudTrail for full auditing of DNS query patterns and configuration changes.

High Availability

End-points are provisioned across multiple Availability Zones automatically to ensure zero downtime.

Fully Managed

No servers to patch or scale. AWS handles the underlying infrastructure of the DNS resolver service.

© 2023 Cloud Architecture Series | Route 53 Resolver Technical Overview

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top