{"id":22648,"date":"2026-07-24T02:50:04","date_gmt":"2026-07-24T02:50:04","guid":{"rendered":"https:\/\/scannn.com\/cloudflare-internal-dns-is-now-generally-available\/"},"modified":"2026-07-24T02:50:04","modified_gmt":"2026-07-24T02:50:04","slug":"cloudflare-internal-dns-is-now-generally-available","status":"publish","type":"post","link":"https:\/\/scannn.com\/lv\/cloudflare-internal-dns-is-now-generally-available\/","title":{"rendered":"Cloudflare Internal DNS is now generally available"},"content":{"rendered":"\n
\n

Starting today, Cloudflare Internal DNS is generally available. Cloudflare Internal DNS provides authoritative and recursive DNS for private networks on the same global network and control plane customers already use for public DNS, Zero Trust, networking, and application services.<\/p>\n

Internal DNS \u2014 sometimes also referred to as private DNS \u2014 is one of the last pieces of enterprise infrastructure still managed separately from the rest of the network. Many organizations operate one platform for public DNS, another for internal DNS, and use cloud-native DNS services inside each cloud environment with separate security policies layered on top. None of these systems share a common control plane. Split-horizon DNS adds another layer of complexity, often requiring multiple DNS environments to remain synchronized so internal and external users receive different answers for the same hostname. When those systems drift, outages follow.<\/p>\n

With Cloudflare Internal DNS, you get a single platform to manage public and private DNS resources, enforcing DNS policies<\/u><\/a> and gaining visibility across your entire DNS stack. For Enterprise customers, this is included with Cloudflare Gateway<\/u><\/a> without any additional charge.<\/p>\n

Why customers are adopting Internal DNS<\/h2>\n

Consolidate DNS operations<\/strong>. Public and private DNS run on one platform, with one API, one audit trail, and one place to set policy. The appliance refresh cycle and the scaling bottlenecks that came with legacy DNS go away.<\/p>\n

Simplify split-horizon DNS<\/strong>. Internal and external resolution are defined as separate views over shared zones, managed from a single control plane. There are no parallel systems to keep in sync, so there’s no drift to chase down.<\/p>\n

Extend Zero Trust to DNS<\/strong>. Resolver policies decide which users and devices resolve against which view, enforced by the same Cloudflare Gateway that already governs the rest of your traffic. Private name resolution stops being the gap in an otherwise Zero Trust architecture.<\/p>\n

Modernize legacy infrastructure<\/strong>. Retire hardware appliances, legacy DNS servers, and cloud-locked resolvers. Cloudflare Internal DNS runs on the infrastructure behind 1.1.1.1, with no hardware to rack and no capacity to provision.<\/p>\n

What we built<\/h2>\n

Cloudflare Internal DNS consists of two components: Gateway Resolver<\/strong> and Internal Authoritative DNS<\/strong>. Authoritatively managing zones is a different job from enforcing DNS security and routing policies.<\/p>\n

\n
\"\"<\/div>\n<\/figure>\n

The Gateway Resolver handles recursive resolution and policy evaluation. Launched in 2020<\/u><\/a> and powered by 1.1.1.1 for public resolution, it comes with a built-in policy engine that can filter DNS queries and redirect queries to different upstream sources \u2014 all based on flexible expressions<\/u><\/a>, with comprehensive logging and audits feeding a single pane of glass.<\/p>\n

Internal Authoritative DNS serves records for internal zones built on the same authoritative platform Cloudflare has operated for over a decade and that serves more domains<\/u><\/a> than any other provider.<\/p>\n

There are three primary objects customers work with:<\/p>\n