# Conditional DNS Forwarding

Conditional DNS forwarding sends DNS queries for specified domain names to designated DNS servers while other queries follow the resolver’s normal resolution process.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/conditional-dns-forwarding

> Conditional DNS forwarding connects separate DNS namespaces without copying their records into every environment. In hybrid and multicloud networks, it lets cloud workloads resolve corporate names and on-premises clients resolve private cloud names through explicitly configured DNS paths.

Practice exams covering Conditional DNS Forwarding: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Conditional DNS Forwarding

Conditional DNS forwarding combines suffix-based routing, explicit namespace ownership, reachable DNS endpoints, and carefully scoped policies to connect separate DNS environments.

1. **Domain-based query selection**: Forwarding policies match queried domain suffixes rather than application ports or destination IP ranges. More-specific suffix rules generally take precedence over broader matching rules.
2. **Separate resolution directions**: Cloud-to-corporate and corporate-to-cloud resolution require their own forwarding configuration. An outbound forwarding path does not automatically provide an inbound DNS service.
3. **Preserved namespace ownership**: The destination DNS system retains responsibility for its namespace. Forwarding avoids duplicating zone records, although cached answers remain subject to TTLs and negative caching.
4. **Explicit network reachability**: Forwarding endpoints need working routes, return paths, and permitted DNS traffic to their targets. Allow both UDP and TCP port 53 for standard DNS, and restrict access to authorized clients and resolvers.
5. **Controlled cross-account and regional scope**: Network connectivity does not automatically distribute DNS policies or private zone visibility. Explicit rule sharing, VPC associations, and regional deployment keep resolution behavior predictable.
6. **Resilience and loop prevention**: Use redundant endpoints and target servers, and define a clear destination for each private namespace. Test overlapping rules and failure behavior to prevent forwarding loops, unintended public fallback, and dependence on a single DNS server.

## Conditional DNS Forwarding exam questions

Real practice exam questions on Conditional DNS Forwarding, with the correct answer and its explanation.

### Question 1 (SAP-C03)

**Question:**

A company uses two on-premises recursive DNS servers to resolve records in an Amazon Route 53 private hosted zone. The servers conditionally forward queries for aws.corp.example.com to the IP addresses of a default Route 53 Resolver inbound endpoint. The endpoint has IP addresses in two Availability Zones, and its VPC is associated with the private hosted zone. Connectivity uses AWS Direct Connect.

After an application deployment adds larger DNS record sets, on-premises clients intermittently experience resolution failures. Packet captures show that small UDP responses succeed. For larger responses, the DNS servers receive a truncated UDP response and retry over TCP, but the TCP connections time out. The same records resolve successfully from instances using the VPC Resolver.

Both endpoint subnets have correct routes. Their network ACLs permit DNS traffic and the required return traffic in both directions. The endpoint security group permits inbound UDP port 53 from the two on-premises DNS server IP addresses and allows all outbound traffic.

Which change will resolve the failures while maintaining least-privilege access and the existing DNS architecture?

**Correct answer:** Add an inbound security group rule allowing TCP port 53 from the two on-premises DNS server IP addresses. Retain the existing UDP rule and conditional forwarding targets.

**Explanation:** A default Resolver inbound endpoint requires inbound access on both UDP and TCP port 53. The on-premises resolvers correctly forward the applicable namespace to the inbound endpoint IP addresses, but their TCP retries are blocked by the endpoint security group. Restricting the new rule to the two DNS server IP addresses preserves least privilege.

### Question 2 (ANS-C01)

**Question:**

A company has a networking account and 30 application accounts in an AWS Organizations organizational unit (OU). All VPCs are in the same AWS Region. The networking account has a Route 53 Resolver outbound endpoint and a forwarding rule for corp.example.com that targets on-premises DNS servers. The rule is associated with the networking VPC, where name resolution works correctly. Only the networking VPC has connectivity to the on-premises DNS servers.

Applications must continue using their VPC-provided DNS resolver. The company wants application teams to enable resolution of corp.example.com in selected VPCs without deploying additional Resolver endpoints or granting application accounts permission to modify the central forwarding configuration. Resource sharing within AWS Organizations is enabled.

Which solution meets these requirements?

**Correct answer:** Share the existing forwarding rule with the application OU through AWS RAM. Have each application account associate the shared rule with its selected VPCs.

**Explanation:** AWS RAM can share Route 53 Resolver forwarding rules across accounts. Each application account can associate the shared rule with its own VPCs without gaining permission to modify the rule. Matching queries use the rule's central outbound endpoint, so the application VPCs do not need their own endpoints or direct connectivity to the on-premises DNS servers.

## Practice Conditional DNS Forwarding in a full exam

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

- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 4 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 4 questions

## What is Conditional DNS Forwarding

Conditional DNS forwarding is a resolver policy that selects a destination DNS server according to the name being queried. For example, a resolver can forward queries for corp.example.com and its subdomains to corporate DNS servers while resolving public internet names normally. Where multiple forwarding rules match, resolvers generally select the most specific matching domain suffix. A rule for engineering.corp.example.com therefore takes precedence over a broader rule for corp.example.com.

The forwarding resolver does not become authoritative for the forwarded namespace and does not replicate its records. Instead, it asks a designated server to resolve matching queries and typically caches the responses according to their TTLs. This differs from DNS delegation, which uses authoritative DNS records to direct resolution toward servers responsible for a child zone. Conditional forwarding is configured on the resolver serving the client, rather than established through the authoritative DNS hierarchy.

In a hybrid deployment, cloud applications might need to resolve database.corp.example.com using an on-premises DNS server. The cloud resolver forwards matching queries through an outbound DNS path over a VPN or private connection. In the opposite direction, corporate DNS servers can conditionally forward a private cloud namespace, such as aws.example.com, to an inbound cloud resolver endpoint. These are separate query directions; configuring one does not automatically enable the other.

On AWS, Amazon Route 53 Resolver outbound endpoints and forwarding rules provide the cloud-to-corporate path. Associate the relevant rules with the VPCs whose workloads need them. For corporate-to-cloud resolution, configure corporate forwarders to use Route 53 Resolver inbound endpoint IP addresses. The private hosted zone must be associated with the VPC receiving inbound queries, or otherwise be available through supported DNS configuration. Do not target the VPC-provided resolver address directly from on premises; use supported inbound endpoints.

Across accounts, a shared networking account can host outbound endpoints and share forwarding rules through AWS Resource Access Manager. Participating accounts associate those rules with their VPCs. Resolver endpoints and forwarding rules are Regional resources, so a multi-Region design needs explicit regional deployment and association planning. VPC peering or a transit gateway supplies network connectivity, but neither automatically shares forwarding rules nor makes every private hosted zone visible to every connected VPC.

Successful forwarding requires more than a correct suffix. Routing, return paths, security groups, network ACLs, and DNS server access controls must permit the exchange. Standard DNS commonly uses UDP port 53, but TCP port 53 is also necessary for responses that require TCP, including fallback after truncation. Use redundant target servers and endpoint addresses across failure domains, and verify reachability from the actual forwarding endpoints. A private network path does not by itself encrypt DNS traffic.

Namespace overlap requires careful planning. A private zone can hide public records under the same domain, and a negative answer from the selected private namespace does not generally trigger a search of the public namespace. In Route 53 Resolver, an equally named forwarding rule takes precedence over a private hosted zone. Avoid forwarding loops in which corporate and cloud resolvers send the same namespace back to each other. Broad root-domain forwarding also needs caution because it can send unrelated queries across the hybrid link and make cloud resolution depend on corporate DNS availability.

Centralized forwarding reduces configuration duplication but adds endpoint cost, network dependency, and operational concentration. Distributed forwarding can improve regional independence at the expense of more infrastructure and policy management. Validate both directions with known records, check negative responses and TTL behavior, and use resolver query logs alongside network diagnostics. Finally, distinguish name resolution from application connectivity: receiving a private IP address does not establish a route, authorize access, or open the application's port.

## Learn Conditional DNS Forwarding in lessons

2 short lessons on Conditional DNS Forwarding in 1 certification course.

- SAP-C03: Conditional DNS Forwarding: bidirectional hybrid resolver paths (Premium), https://app.blowstack.com/lessons/conditional-dns-forwarding-bidirectional-hybrid-resolver-paths-sap-c03
- SAP-C03: Conditional DNS Forwarding vs. Split-Horizon DNS (Premium), https://app.blowstack.com/lessons/conditional-dns-forwarding-vs-split-horizon-dns-sap-c03
