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.
Trace conditional forwarding between on-premises DNS and VPCs in both directions.
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.
- VPC application → VPC ResolverIdentify query source
- VPC Resolver → Outbound endpointMatch a suffix
- 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
| Query source | Namespace | What to inspect |
|---|---|---|
| AWS application | corp.example | Outbound endpoint and forwarding rule |
| On-premises client | app.example | Inbound endpoint and site forwarding |
| AWS application | Ordinary public name | No site forwarding needed |
| Site client | app.example resolves; connection fails | Inspect 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.
Check, then explain in your own words
- List query sources and names.
- Separate the two endpoint directions.
- 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.
- What is Route 53 VPC Resolver?Checked:
Scope and conditionsDirection of inbound and outbound endpoints and conditional forwarding.
Used in this lessonFollow the query from its origin Separate name resolution from application access Limit forwarding to the intended scope