Cloud concept · Updated

Conditional Forwarding - Conditional forwarding directs DNS queries for selected domain names to designated DNS servers instead of using the resolver’s normal resolution path.

In short

A DNS resolver matches a query name against configured domain suffixes and forwards matching queries to specified upstream servers. This allows cloud and on-premises environments to resolve each other’s private namespaces without publishing private records or copying entire DNS zones.

Cloud Concepts Hub →

6 key aspects of Conditional Forwarding

Conditional forwarding combines domain-based query routing with explicit namespace ownership, directional connectivity, precedence rules, and resilient DNS infrastructure.

01
Domain-based query selection

Forwarding rules select an upstream DNS destination using the queried domain suffix. Use explicit namespace boundaries and more-specific rules where different subdomains have different resolution owners.

02
Independent resolution directions

Cloud-to-on-premises and on-premises-to-cloud resolution require separate configurations. An outbound forwarding path does not automatically provide an inbound path.

03
Separation from DNS authority

Forwarding routes queries without transferring zone ownership or copying records. Use delegation for authoritative namespace boundaries and forwarding for resolver-specific query routing.

04
Network and availability dependencies

DNS targets must be reachable through working routes and security controls, with UDP and TCP supported where conventional DNS is used. Distribute endpoints and upstream servers across failure domains and test failover behavior.

05
Explicit namespace precedence

Overlapping rules and authoritative zones can change which system answers a query. Document precedence and negative-response behavior instead of assuming unresolved private names fall back to public DNS.

06
Controlled sharing and regional scope

Shared forwarding policies can reduce configuration drift across accounts, but associations and regional deployment remain explicit. Rule sharing does not grant access to private zones or create network connectivity.

Conditional Forwarding exam questions

Real practice exam questions on Conditional Forwarding, with the correct answer and its explanation. Answer them with every option in the exam simulator.

SAP-C03

A company connects its data center to a shared-services VPC through AWS Direct Connect. The company's on-premises recursive DNS servers are authoritative for corp.internal. For all other namespaces, these servers forward queries to Amazon Route 53 Resolver inbound endpoint IP addresses in the shared-services VPC.

The shared-services VPC has a private hosted zone named aws.internal and a Resolver outbound endpoint. A forwarding rule for the root domain (.) is associated with the VPC and targets the on-premises DNS servers. Routing and security controls permit all required DNS traffic.

During testing, AWS workloads can resolve corp.internal records, and on-premises clients can resolve aws.internal records. However, queries for uncached public internet names time out from both environments. Query logs show the same public DNS queries repeatedly passing between the environments.

Company policy requires public DNS resolution for both environments to pass through Route 53 Resolver in the shared-services VPC, where centralized DNS filtering is applied. Corporate DNS records must remain authoritative on premises and must not be copied to AWS.

Which change will meet these requirements?

Show answerCORRECT ANSWER

Replace the root-domain outbound forwarding rule with a rule for corp.internal that targets the on-premises DNS servers. Associate the replacement rule with the shared-services VPC and leave the on-premises forwarding configuration unchanged.

Only corporate namespace queries need the outbound path. Restricting that path to corp.internal breaks the loop for public names, which Route 53 Resolver can resolve normally with centralized filtering. On-premises queries for other namespaces still enter through the inbound endpoint, where the private hosted zone and public resolution remain available.

ANS-C01

A company centralizes hybrid DNS in a networking account. Application VPCs use AmazonProvidedDNS and have an associated Route 53 Resolver forwarding rule for corp.example.com. The rule sends queries through a central outbound endpoint to two on-premises recursive DNS servers.

A private hosted zone named aws.corp.example.com contains the company's AWS application records. It is associated with all application VPCs and the central VPC, which contains a Resolver inbound endpoint. No other private hosted zones or Resolver rules overlap these namespaces.

The on-premises recursive DNS servers normally resolve corporate names through an internal DNS hierarchy that is not accessible from AWS. To enable on-premises access to AWS records, an administrator configures these servers to conditionally forward corp.example.com to the inbound endpoint. Queries from AWS for existing on-premises names such as payroll.corp.example.com now time out. Packet captures show the queries repeatedly traveling between the outbound endpoint, the on-premises recursive servers, and the inbound endpoint. Routing and DNS traffic permissions are correct.

Which change will eliminate the forwarding loop while preserving resolution of both environments' private records and normal public DNS resolution, without copying records?

Show answerCORRECT ANSWER

Change the on-premises conditional forwarding suffix from corp.example.com to aws.corp.example.com. Retain the AWS forwarding rule for corp.example.com.

Only the AWS-owned child namespace needs to be forwarded from on premises to the inbound endpoint. Other corporate queries then follow the on-premises servers' existing internal resolution path. AWS queries for corporate records still use the outbound rule, while the more-specific aws.corp.example.com private hosted zone provides AWS records. Unrelated public queries retain their normal resolution path.

Practice Conditional Forwarding in a full exam

Questions on Conditional Forwarding in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Conditional Forwarding

3 min read

Conditional forwarding is a DNS resolution policy based on the name being queried. For example, a resolver can send queries for corp.example.com and its descendants to corporate DNS servers while resolving unrelated names through its normal path. The destination server might answer authoritatively or perform further resolution. Forwarding does not transfer ownership of the namespace, replicate zone records, or change the application traffic path.

Rules normally match complete DNS labels and their descendants, not arbitrary text fragments. When multiple forwarding rules match, the most specific matching domain generally takes precedence. A rule for engineering.corp.example.com therefore takes priority over one for corp.example.com. Exact interactions between forwarding rules, locally authoritative zones, and default resolution policies depend on the resolver implementation and must be checked explicitly.

A typical hybrid design uses separate forwarding paths in each direction. Cloud workloads send queries for corp.example.com through a cloud resolver to on-premises DNS servers. Corporate DNS servers forward queries for aws.example.com to a cloud ingress resolver that can resolve the relevant private cloud zones. Neither direction automatically enables the other. Distinct namespace boundaries also help prevent loops in which both environments forward the same unresolved queries back to each other.

In AWS, workloads normally query the VPC-provided Route 53 Resolver. A forwarding rule associated with the workload VPC sends matching queries through a Route 53 Resolver outbound endpoint to specified DNS server IP addresses. For the reverse direction, an on-premises conditional forwarder targets the IP addresses of a Resolver inbound endpoint. That endpoint accepts queries into the resolver context of its VPC, where the required private hosted zones must be available. Do not target the VPC-provided resolver address directly from on-premises networks.

Resolver endpoints require network connectivity; they do not create it. AWS Direct Connect or a Site-to-Site VPN can provide the private path, but routes, security groups, network ACLs, and on-premises firewalls must also permit DNS traffic. For conventional DNS forwarding, support both UDP and TCP port 53: TCP is required for some responses and retries. Inbound endpoint security groups permit queries from approved clients, while outbound endpoint security groups permit queries to the target DNS servers. Deploy endpoint IP addresses across at least two Availability Zones and provide redundant upstream DNS servers.

Multi-account designs can centralize outbound endpoints and share forwarding rules through AWS Resource Access Manager. Each consuming VPC still needs the appropriate rule association; sharing a rule does not share private hosted zones or establish application connectivity. Resolver endpoints and rules are Regional resources, so multi-Region designs require deliberate regional deployment and associations. VPC peering or a transit network alone does not automatically expose every private DNS namespace.

Forwarding and delegation solve different problems. Delegation uses NS records in a parent zone to identify the authoritative servers for a child zone. Conditional forwarding is resolver configuration that selects an upstream destination. A private hosted zone stores authoritative records; a forwarding rule tells the resolver where to send queries. Route 53 alias records, traffic policies, and health checks influence answers or endpoint selection, not the conditional forwarding path.

Overlapping namespaces require particular care. In Route 53 Resolver, a forwarding rule takes precedence over a private hosted zone with the same domain name. When resolution selects a private hosted zone and the requested record is absent, Resolver does not fall back to the public version of that zone. Likewise, a negative response from an upstream server is not ordinarily a signal to try public DNS. Forwarding failures, authoritative negative responses, and cached negative responses are different troubleshooting cases.

The main trade-offs are added latency, endpoint and connectivity costs, and dependence on remote DNS availability. Caching reduces repeated queries but can delay visibility of record changes until TTLs expire. Configure reverse lookup forwarding separately when PTR resolution is required, using the appropriate in-addr.arpa or ip6.arpa namespace. Validate representative queries in both directions, inspect query logs and endpoint metrics, and test upstream-server and network-path failures rather than assuming multiple configured targets guarantee availability.

Learn Conditional Forwarding in lessons

2 short lessons on Conditional Forwarding in 1 certification course.

Open the lessons