INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

Topic lessonTopic: Connecting VPCs and investigating traffic

Route 53 VPC Resolver hybrid DNS: direction and conditional forwarding

Start with who asks the question and which side owns the answer. Trace conditional forwarding between on-premises DNS and VPCs in both directions.

What you will learn

Trace conditional forwarding between on-premises DNS and VPCs in both directions.

Prerequisite

This scenario uses fictional private names. No real DNS configuration is changed.

Follow the query from its origin

Outbound endpoints send selected AWS-originated questions to external resolvers. Inbound endpoints accept DNS queries coming into the VPC Resolver.

A VPC application resolves an internal site name
A VPC application resolves an internal site name1: VPC application — Identify query source — VPC Resolver. 2: VPC Resolver — Match a suffix — Outbound endpoint. 3: Outbound endpoint — Forward to the answer source — Site DNS123VPC applicationVPC ResolverOutbound endpointSite DNSA VPC application resolves an internal site name1: VPC application — Identify query source — VPC Resolver. 2: VPC Resolver — Match a suffix — Outbound endpoint. 3: Outbound endpoint — Forward to the answer source — Site DNS123VPC applicationVPC ResolverOutboundendpointSite DNS
  1. VPC application → VPC ResolverIdentify query source
  2. VPC Resolver → Outbound endpointMatch a suffix
  3. Outbound endpoint → Site DNSForward to the answer source
VPC application
Name in corp.example
VPC Resolver
Selects the forwarding rule
Outbound endpoint
Sends query to site DNS
Site DNS
Answers for its zone

Separate name resolution from application access

The site resolves corp.example and the VPC hosts app.example privately.
Query sourceNamespaceWhat to inspect
AWS applicationcorp.exampleOutbound endpoint and forwarding rule
On-premises clientapp.exampleInbound endpoint and site forwarding
AWS applicationOrdinary public nameNo site forwarding needed
Site clientapp.example resolves; connection failsInspect actual traffic to the answer

Forwarding rules select names to send onward. A correct answer still needs a separate application connection test.

Limit forwarding to the intended scope

Identify the side hosting each zone. Record the query origin and answer source. Inspect conflicting forwarding rules for cyclic dependencies.

Keep the vantage point fixed. Record a lookup and connection outcome from the same client while keeping them distinct.

Review requirements before extending coverage. Check destination, necessary network access, associated VPC and response to forwarding failures.

Check the worked example

Choose an option to see the result and explanation.

Which endpoint forwards a VPC query to site DNS?
Read the answer and reason

Answer: Outbound · The query is leaving the VPC resolver.

Which endpoint receives site queries for private VPC names?
Read the answer and reason

Answer: Inbound endpoint · AWS receives the forwarded query at an inbound endpoint.

DNS succeeds and the connection fails. What next?
Read the answer and reason

Answer: Verify the actual connection from the same source · The answer and reachability are separate observations.

Check, then explain in your own words

  1. List query sources and names.
  2. Separate the two endpoint directions.
  3. Check actual connections from the same vantage point.
Check your understanding: Does resolving a private name from the site establish application recovery?

Verify connectivity to the answer and the workload outcome separately.

DNS success is one stage in access.

Sources and conditions checked

The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.