Split-horizon DNS means one domain name returns different answers depending on who asks. An employee on the office network gets a private IP for app.example.com, and a visitor on the internet gets the public one. You build it with separate views, zones or servers, and you keep it healthy by keeping both copies in sync and watching which resolver each client really uses. This guide covers how it works, when to use it, how to configure it, and how it relates to CNAME flattening and alias records, which people often confuse with it.
TL;DR
- Split-horizon DNS (also called split-view, split DNS or split-brain DNS) serves different records for the same name to internal and external clients, usually chosen by the client's source address.
- Use it to keep internal hostnames and private IPs out of public DNS and to send internal users straight to private addresses.
- The main risks are zones drifting out of sync, resolver caching, and NAT or VPN moving a client into the wrong view.
- CNAME flattening and alias records are a different thing: they solve the "no CNAME at the apex" problem, not the internal-versus-external problem.
- Verify every change from both sides of the boundary with
dig, a traceroute and an external check.
Table of Contents
- What split-horizon DNS actually is
- Why organizations use it
- Three common ways to build it
- Where split-horizon DNS goes wrong
- Troubleshooting checklist
- Split horizon is not CNAME flattening
- Our perspective
- Check your DNS changes with Pingfloat
- A sensible rollout plan
- FAQ
- Sources
What split-horizon DNS actually is
The terms split DNS, split-horizon DNS, split-view DNS and split-brain DNS are used interchangeably for providing different sets of DNS information, usually selected by the source address of the request. If someone tells you they run "split brain DNS", they almost certainly mean the same design you would call split horizon.
The IETF gives a more formal definition. In a draft from its ADD working group, split-horizon DNS is the service provided by a resolver that also acts as an authoritative server for some names, returning results that differ meaningfully from the global DNS. Those names resolve that way only from inside the network.
A concrete example makes it clear. Say your company owns example.com:
| Who asks | Query | Answer |
|---|---|---|
| Laptop on the office LAN | intranet.example.com | 10.20.4.15 (private) |
| Customer on the internet | intranet.example.com | No record, or a public gateway IP |
| Laptop on the office LAN | www.example.com | Public IP, same as everyone else |
The name is the same. The answer depends on the asker. If you need a refresher on why a private address cannot be routed from the internet, our guide to public vs private IP addresses covers the basics.
Why organizations use it
Security and privacy
The Center for Internet Security's BIND benchmark names two goals for a split-horizon architecture: minimize the amount and type of externally available information, and separate external and internal DNS services physically and logically, so that a compromised external name server does less damage. That benchmark dates from January 2006, but the reasoning still holds. Public DNS should not publish the names of your database servers, build hosts or admin panels.
Tailscale makes a similar argument in its explainer on split DNS: it can hide internal resource names from external clients and reduce some attack opportunities by limiting exposure. Hiding a name is not access control, though. Treat it as one layer next to firewalls and authentication, never a substitute.
Shorter paths for internal users
A common case is a server that has both a private LAN address and a public address. With split-horizon DNS the same name can lead to either one, depending on the client, which can reduce latency by cutting the number of network devices traversed. Without it, internal users often hit the public IP, loop out through the firewall and come back in (hairpin NAT), or fail outright when the firewall does not allow that.
Cloud and Kubernetes
The pattern is not limited to office networks. The external-dns project documents split horizon for clusters: internal clients receive private ClusterIP addresses while external clients receive public load balancer IPs. It supports internal/external separation, multiple DNS providers and geographic splits.
Three common ways to build it

1. Views in BIND 9
In BIND, a view is a separate copy of the DNS namespace. For each query, BIND checks the views in order and uses the first one whose match-clients list contains the client's source IP. A minimal sketch looks like this:
acl internal { 10.0.0.0/8; 192.168.0.0/16; };
view "internal" {
match-clients { internal; };
zone "example.com" {
type master;
file "db.example.com.internal";
};
};
view "external" {
match-clients { any; };
zone "example.com" {
type master;
file "db.example.com.external";
};
};
Order matters. Put the most specific view first, and the catch-all any view last. Each view needs its own copy of every zone it serves, including zones that are identical in both.
2. DNS policies on Windows Server
Microsoft's approach evaluates every query against policies on the server. Using the server interface as the criterion, queries that arrive on the private interface get answers from the internal zone scope, and queries on the public interface get the default answers. The details are in Microsoft's split-brain deployment guide, which describes two versions of one zone served by the same server using policies and zone scopes. If you are planning this alongside a wider rollout, the multi-site network design article from nfd.ca walks through split-brain DNS on a DNS server with policies and query interfaces.
3. A child zone for internal names
ISC describes a simpler option in its private networks and split DNS article: make a single internal zone that is a child of the external one, such as internal.example.com instead of reusing example.com. The listed advantages are that resolution just works, names outside the internal domain give the same answers everywhere, and DNSSEC validation for internal clients works when configured properly.
This is often the cleanest design for a new network. You avoid maintaining two copies of the same zone, and the question "which view did this client land in?" mostly disappears.
Where split-horizon DNS goes wrong
The failures are predictable. A write-up on common split-horizon pitfalls lists three that matter most:
- Caching. Resolvers cache responses, so internal and external resolvers must be kept separate. A shared caching resolver can hand an internal answer to an outside client or the other way round.
- Drift. Each view has its own copy of the zone. Miss an update in one and inside and outside quietly disagree.
- Source-address selection. Because the view is chosen by source IP, NAT or a VPN can place a client in a view you did not intend.
There is a deeper structural issue too. The IETF draft on split-horizon authority notes that clients using pure stub resolution always receive split-horizon results, while clients that use a different resolver, such as a public DNS service configured in the browser or OS, never do. That is why "it works on my laptop but not on the phone" is the classic symptom.
DNSSEC
DNSSEC can coexist with split DNS. ISC's documentation says validation for internal clients works for names in the internal zone, provided the DS records are set up so the chain from the root through com to example.com can complete for the internal name. If you reuse a signed public zone name internally with different data, validation will fail for that data. The child zone design above avoids most of this.
Troubleshooting checklist
Work from the client outward. Our DNS troubleshooting guide goes deeper on the commands, and the DNS misconfiguration walkthrough covers fixes. For split horizon specifically:
- Find out which resolver the client uses. Check the OS resolver settings, VPN client and browser "secure DNS" options. A browser with its own DNS-over-HTTPS resolver skips your internal view entirely.
- Query the internal resolver directly. Run
dig @10.0.0.53 intranet.example.comand confirm the private answer. - Query a public resolver. Run
dig @1.1.1.1 intranet.example.comand confirm it returns nothing or the public answer you intend. - Compare the zone serial or content in each view. If the two copies should match for shared names, diff them.
- Check TTLs. A long TTL on a record you just changed keeps old answers alive. The TTL math article explains how to plan this.
- Confirm the delegation. The NS record reference shows what the public side should be delegating.
- Trace the path. If the name resolves correctly but the connection fails, run a traceroute from both inside and outside to see where packets stop.
Split horizon is not CNAME flattening
People searching for split DNS often also land on CNAME flattening and alias records. The topics share a vocabulary (records, answers, apex), but they solve unrelated problems.
- Split horizon changes the answer based on who asks.
- CNAME flattening and alias records change the shape of the answer so you can point a zone apex at a hostname.
The apex problem
A CNAME record says one name is an alias of another, and it must point to a domain, never to an IP address. Under the DNS rules a CNAME cannot coexist with other records at the same name, and the apex of a zone always carries SOA and NS records, so you cannot place a CNAME there. If your hosting provider gives you a hostname rather than an IP, you have a problem at example.com. If you want the fundamentals of choosing between record types, see A vs CNAME record, plus the references for A records and AAAA records.
What CNAME flattening does
Cloudflare's CNAME flattening documentation describes it this way: the DNS provider follows the CNAME chain to the final IP address and returns that IP instead of the target hostname. That speeds up resolution and allows CNAME-like behavior at the apex. The documentation also warns about a dangling CNAME, where the final target has no A or AAAA records. Flattening then returns an empty response (NODATA), which can look like the record is not propagating.
Flattening also touches split DNS in one place. In Cloudflare's internal DNS records documentation, flattening is applied by default for internal DNS and cannot be turned off. If flattening fails, the CNAME is returned as-is to the Gateway resolver, which can fall back to public DNS if that option is enabled.

Alias records versus CNAME records
An alias record is the provider-specific cousin of flattening. Two major cloud DNS services document it:
| CNAME | Alias record | |
|---|---|---|
| Allowed at apex | No | Yes |
| Query types answered | Any, the resolver follows the name | Only matching A or AAAA |
| Who resolves the target | The client's resolver | The provider's name server |
| Portability | Standard DNS | Provider-specific |
AWS says alias records are Route 53-specific extensions that work at the zone apex, and that they require the query type (A or AAAA) to match the alias record type, while CNAMEs redirect regardless of query type. Google Cloud's DNS records overview says its ALIAS records can be used only at the apex, respond only to A or AAAA queries, and are not compatible with DNSSEC. There, the name server resolves the canonical name and synthesizes A and AAAA records.
The practical rule: use a CNAME for subdomains, and use flattening or an alias record at the apex if your DNS provider offers one. Check your own provider's documentation for its exact behavior, since the details differ.
Our perspective
Most split-horizon incidents we hear about are not exotic. Someone changed a record in one view and forgot the other, or a client was quietly using a resolver nobody planned for. The design is simple. The discipline around it is what takes effort.
That is why we think DNS work should always be checked from outside your own network, not just from the machine you configured it on. A record that looks right from inside tells you nothing about what the world sees. Pair a quick
digwith an external check of the public side, then repeat after every change.We build Pingfloat as a set of free web tools, with core functions that need no installation or account, so that checking from a different vantage point takes seconds. Traceroute, SSL checks and uptime monitoring are one click away, and the DNS reference pages explain each record type in plain words. If a name has to stay reachable, we think you should monitor it, not assume it.
Andreas
Check your DNS changes with Pingfloat
Split-horizon changes are easiest to trust when you can see the public side from outside your network. Pingfloat offers a free suite of web tools for developers and IT professionals, and the ones that help here are the traceroute tool for following the path to a host, the SSL checker for confirming that the public name serves the certificate you expect, and the uptime monitor for watching a public hostname over time.

Core tools work without an account. Signing up adds extras such as scheduled uptime monitoring and saved results. You can browse everything on the Pingfloat home page, or automate checks through the Pingfloat public API.
A sensible rollout plan
If you are adding split horizon to an existing network, a staged approach limits surprises.
- Inventory names. List which names must be public, which must be internal only, and which must be both with different answers. Most names fall in the first or third group.
- Pick the design. For a new internal namespace, prefer a child zone like
internal.example.com. For existing names that must differ inside, use views or policies. - Separate the resolvers. Internal clients should use an internal recursive resolver. External queries should reach only the authoritative server for the public zone. Do not let one cache serve both.
- Automate the copy. If two zones share records, generate both from one source rather than editing by hand. This removes the drift risk.
- Handle VPN and remote staff. Decide which view a VPN client should land in, and make sure its DNS settings point to the internal resolver.
- Test from both sides. Use the checklist above, and repeat after every change.
- Monitor the public names. A public record that stops resolving is the failure customers notice first.
FAQ
What is split-horizon DNS in simple terms?
It is a setup where the same domain name returns different DNS answers depending on who is asking. Internal users typically get private IP addresses, and outside users get public ones. The server usually decides based on the source address of the query.
Is split DNS the same as split-brain DNS?
In everyday use, yes. Split DNS, split-horizon, split-view and split-brain are used interchangeably for serving different DNS information to different clients. Vendors may favor one term, but the design is the same: two versions of one namespace.
Does split-horizon DNS replace a firewall?
No. It limits what names an outsider can discover, but it does not block access to an IP address that someone already knows. Use it together with network controls and authentication, as the CIS benchmark frames it: as a way to minimize exposed information and limit damage if the external server is compromised.
What is the difference between CNAME flattening and an alias record?
Both let you point a zone apex at a hostname. Flattening follows the CNAME chain and returns the final IP, while an alias record is a provider-specific record type that is resolved by the provider and returns A or AAAA answers. Neither is related to split horizon, which is about who asks rather than what shape the answer takes.
Why does my internal name work on one device but not another?
The device is probably using a different resolver. Pure stub resolvers get split-horizon answers, while devices using a public resolver or a browser's own secure DNS never do. Check the device's DNS settings and any VPN client first.
Sources
- Split-horizon DNS authority draft (IETF, May 2024)
- Split-horizon authority draft, later revision (IETF, June 2024)
- What is Split-Horizon DNS? (splitdns.net)
- Use DNS Policy for Split-Brain DNS Deployment (Microsoft Learn)
- Split Horizon DNS (external-dns)
- Private networks and split DNS (ISC)
- CIS DNS BIND Benchmark v1.0
- What is Split DNS & Why Should You Use It? (Tailscale)
- Split-horizon DNS with BIND on Ubuntu (CubePath)
- Split-Horizon DNS: One Name, Two Answers (DEV)
- CNAME flattening (Cloudflare DNS docs)
- Manage internal DNS records (Cloudflare DNS docs)
- Choosing between alias and non-alias records (Amazon Route 53)
- DNS records overview (Google Cloud)
- Multi-site network design for SMBs (nfd.ca)
