# Split-Horizon DNS

Split-horizon DNS provides different DNS answers for the same domain name depending on the querying client's DNS resolution context, such as its network or resolver.

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

> Split-horizon DNS maintains separate views of a shared namespace, commonly returning private addresses to internal clients and public endpoints to internet clients. It lets applications use consistent names across environments while controlling which endpoints each audience discovers, but requires careful resolver configuration and coordination between DNS views.

Practice exams covering Split-Horizon DNS: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Split-Horizon DNS

Split-horizon DNS depends on separate namespace views, predictable resolver paths, explicit record management, and network controls that remain independent of DNS.

1. **One namespace, multiple views**: The same hostname can identify different endpoints for internal and external clients. This keeps application configuration consistent while allowing separate private and public access paths.
2. **Resolver-dependent answers**: The resolver path determines which view a client sees. Configure VPN clients, virtual networks, and conditional forwarding so that queries reach the intended DNS infrastructure.
3. **Independent authoritative data**: Public and private zones contain independently managed records. Treat required records in each view as explicit configuration rather than assuming synchronization or fallback.
4. **Hybrid DNS integration**: Conditional forwarding and resolver endpoints extend private resolution across cloud and on-premises networks. Design forwarding direction, domain matching, connectivity, and redundancy together to prevent loops and resolution failures.
5. **Zone and rule precedence**: Overlapping private zones and forwarding rules can change which authority answers a query. Check the platform's matching and precedence rules, especially when a private namespace shadows public records.
6. **Separate DNS from access control**: DNS selects an endpoint but does not establish reachability or permission to use it. Validate routing, network controls, authentication, and TLS independently of name resolution.

## Cloud services for Split-Horizon DNS

Authoritative DNS services hold the records for each namespace view, while private-zone associations or network links define where the internal view is available. Resolver services connect clients to those views and extend resolution across hybrid networks through conditional forwarding. In AWS, Route 53 hosted zones provide the public and private records, and Route 53 Resolver supplies VPC resolution and hybrid endpoints. Azure Private DNS and Google Cloud DNS provide comparable private namespace capabilities in their respective clouds. Across platforms, engineers must coordinate zone visibility, forwarding precedence, record updates, and private connectivity; creating parallel zones alone does not ensure clients receive the intended answers.

- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: Public and private hosted zones can serve different records for the same namespace. Private hosted zone associations determine which VPCs can resolve the private view through their VPC Resolver.

## Split-Horizon DNS exam questions

Real practice exam questions on Split-Horizon DNS, with the correct answer and its explanation.

### Question 1 (SOA-C03)

**Question:**

A company operates production and test environments in separate VPCs in the same AWS Region. Applications in both environments use gateway.example.com. Production workloads must resolve this name to a production service's private IPv4 address, and test workloads must resolve it to a test service's private IPv4 address. Internet clients must continue resolving the same name to the public IPv4 address published in the existing Route 53 public hosted zone for example.com.

Both VPCs use AmazonProvidedDNS, have both required VPC DNS attributes enabled, and have no Resolver forwarding rules. The company must select DNS answers according to the requesting VPC, regardless of endpoint health.

Which configuration meets these requirements?

**Correct answer:** Create two private hosted zones named gateway.example.com. Associate one only with the production VPC and create an apex A record for the production private address. Associate the other only with the test VPC and create an apex A record for the test private address. Retain the existing public record.

**Explanation:** Separate private hosted zones can have the same name when they are associated with different VPCs. Each VPC Resolver uses its associated private zone, so production and test receive their respective private addresses. Internet clients continue resolving the existing public record.

### Question 2 (SAP-C03)

**Question:**

A company hosts its public DNS namespace, example.com, in an Amazon Route 53 public hosted zone. The record api.example.com points to an internet-facing load balancer. Other public records change frequently.

The company is deploying an internal version of the API behind an internal Application Load Balancer in an application VPC. Applications in this VPC and clients in an on-premises data center must resolve api.example.com to the internal load balancer. Internet clients must continue to receive the public answer. All other example.com names must continue to resolve from the public hosted zone without maintaining duplicate records.

The data center connects to a separate shared-services VPC through AWS Direct Connect. Routing between the data center and both VPCs is configured. On-premises recursive DNS servers currently resolve example.com through public DNS and are not authoritative for that namespace. The company requires a managed DNS solution that remains available if one Availability Zone fails.

Which solution meets these requirements?

**Correct answer:** Create a private hosted zone named api.example.com and associate it with both VPCs. At the zone apex, create an alias pointing to the internal load balancer. Deploy a Route 53 Resolver inbound endpoint across two Availability Zones in the shared-services VPC. Configure the on-premises DNS servers to conditionally forward api.example.com queries to both endpoint IP addresses, allowing TCP and UDP port 53 from those servers.

**Explanation:** The narrowly scoped private hosted zone overrides only api.example.com and its descendants, leaving other example.com names to public DNS resolution. Associating the zone with the application VPC enables local workloads to resolve the private answer. Associating it with the shared-services VPC makes that answer available through the inbound endpoint. Conditional forwarding provides the on-premises resolution path, and endpoint IP addresses in two Availability Zones provide Availability Zone resilience.

### Question 3 (ANS-C01)

**Question:**

A company hosts example.com in an Amazon Route 53 public hosted zone. The record api.example.com is an alias to an internet-facing Application Load Balancer (ALB). The zone also contains hundreds of other public records that different teams update frequently.

The company deploys a separate internal ALB across two Availability Zones. Applications in three VPCs must resolve api.example.com to the internal ALB, while internet clients must continue resolving the same name to the internet-facing ALB. All other names under example.com must continue resolving from the public hosted zone without copying or synchronizing those records into a private hosted zone. The VPCs have connectivity to the internal ALB, use the Amazon-provided Resolver, and have both required VPC DNS attributes enabled.

Which configuration meets these requirements with the least ongoing DNS administration?

**Correct answer:** Create a private hosted zone named api.example.com and associate it with all three VPCs. Create an alias A record at the private zone apex targeting the internal ALB. Leave the public hosted zone unchanged.

**Explanation:** The narrowly scoped private zone overrides resolution for api.example.com within the associated VPCs without shadowing unrelated names under example.com. An alias A record is supported at the zone apex and can target the internal ALB. Internet clients continue using the existing public record, and other public records require no duplication.

## Practice Split-Horizon DNS in a full exam

Questions on Split-Horizon DNS in each practice exam, with every answer option and an explanation for each:

- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 13 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 3 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 1 question

## What is Split-Horizon DNS

Split-horizon DNS means that a fully qualified domain name can resolve differently depending on where and how the query is resolved. For example, api.example.com might resolve to an internet-facing load balancer for public users and an internal load balancer for workloads on a private network. The application uses the same hostname in both locations, while DNS directs clients toward an appropriate endpoint. An internal view can also contain names that do not exist in the public view.

The deciding factor is the DNS resolution path, not simply whether a device has a private IP address. An internal client using an external recursive resolver might receive the public answer. A remote employee connected through a VPN receives the internal answer only if the device's DNS configuration sends the relevant queries to a resolver that can access the internal view. Browser-managed encrypted DNS and local resolver overrides can bypass the intended configuration.

In a cloud environment, a common implementation uses public and private authoritative zones with the same domain name. The public zone is delegated through the public DNS hierarchy. The private zone is made available to selected virtual networks through zone associations, network links, or resolver policies. Records in these zones are managed separately; creating or changing a public record does not automatically update its private counterpart.

On AWS, an Amazon Route 53 public hosted zone and private hosted zone can both use example.com. Associate the private hosted zone with the VPCs that need its records and enable the required VPC DNS settings, including enableDnsSupport and enableDnsHostnames. Workloads querying the VPC Resolver then receive matching private-zone records, while internet clients use the public zone. A crucial operational detail is that a matching private zone does not merge with the public zone. If the requested name or record type is missing from that private zone, resolution does not automatically fall back to the public record.

Hybrid networks require an explicit forwarding design. On-premises DNS servers can conditionally forward the cloud namespace to Route 53 Resolver inbound endpoint addresses over private connectivity. For queries originating in a VPC that must reach on-premises DNS, Resolver outbound endpoints and forwarding rules provide the opposite direction. Allow both UDP and TCP port 53 where required, provide resilient endpoint connectivity, and avoid forwarding loops. On AWS, a matching Resolver forwarding rule takes precedence over a private hosted zone for the same domain, so overlapping rules deserve particular attention.

The main trade-offs are duplicated record management, more complicated troubleshooting, and inconsistent answers during changes. Positive and negative caching can preserve old results until their cache lifetimes expire. Test from each intended client network using its actual resolver, compare the returned records and response codes, and verify private-zone associations and forwarding rules before changing application settings.

Split-horizon DNS is not a security boundary or a routing mechanism. Returning a private address does not create network connectivity, and hiding a record does not authorize access. Routes, firewalls, security groups, application authentication, and TLS certificates still need to be correct. It is also distinct from geographic or weighted DNS routing: those policies select answers for traffic distribution, whereas split-horizon DNS separates namespace views for different resolution contexts.

## Learn Split-Horizon DNS in lessons

4 short lessons on Split-Horizon DNS in 2 certification courses.

- SOA-C03: Split-Horizon DNS: public and private namespace views (Premium), https://app.blowstack.com/lessons/split-horizon-dns-public-and-private-namespace-views-soa-c03
- SAP-C03: Split-Horizon DNS: public and private views in hybrid networks (Premium), https://app.blowstack.com/lessons/split-horizon-dns-public-and-private-views-in-hybrid-networks-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
- SAP-C03: Conditional Forwarding vs. Split-Horizon DNS (Premium), https://app.blowstack.com/lessons/conditional-forwarding-vs-split-horizon-dns-sap-c03
