INFRA Signal 207
Cloudflare Internal DNS is now generally available
↗
Engineers can replace fragmented DNS setups—where public, private, and cloud-native resolvers run on separate platforms with independent policies—by managing split-horizon DNS from a single control plane. This eliminates the drift and outages caused by keeping parallel systems synchronized and closes a common visibility gap in Zero Trust architectures.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Split-horizon DNS is implemented through DNS Views and Zone References, allowing a shared zone to be defined once and referenced across multiple resolution contexts rather than duplicated and kept in sync manually.
All record changes flow through a single DNS Records API regardless of origin (dashboard, Terraform, or direct API call), giving engineers one write path to audit and one propagation pipeline to reason about.
The service is included with Cloudflare Gateway for Enterprise customers at no additional charge, running on the same global infrastructure that powers the 1.1.1.1 public resolver.
THE CLUSTER