--- title: Cloudflare Internal DNS is now generally available description: Cloudflare Internal DNS is now generally available for Enterprise customers using Cloudflare Gateway at no additional charge. It unifies public and private DNS... canonical: https://daily.dev/posts/cloudflare-internal-dns-is-now-generally-available-4o5riyin5 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Cloudflare Internal DNS is now generally available | daily.dev og:description: Cloudflare Internal DNS is now generally available for Enterprise customers using Cloudflare Gateway at no additional charge. It unifies public and private DNS... og:url: https://daily.dev/posts/cloudflare-internal-dns-is-now-generally-available-4o5riyin5 og:image: https://api.daily.dev/og/posts/4o5RIYIN5.png og:image:alt: Cloudflare Internal DNS is now generally available og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Cloudflare Internal DNS is now generally available **[Cloudflare](https://daily.dev/sources/cloudflare)** · 7 min read · 35 upvotes · 3 comments ## Summary Cloudflare Internal DNS is now generally available for Enterprise customers using Cloudflare Gateway at no additional charge. It unifies public and private DNS management on a single platform and control plane, eliminating the need for separate internal DNS appliances or cloud-native DNS services. Key features include Internal Zones for private resource records, DNS Views for split-horizon resolution without parallel systems, and Resolver Policies that integrate with Cloudflare Gateway's Zero Trust enforcement. Record changes propagate globally in seconds via the same DNS Records API used for public DNS, with Terraform support available. The service works with WARP, DoH, DoT, standard DNS, and Cloudflare WAN, enabling consistent private name resolution across remote users, branch offices, and cloud environments from one control plane. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is Cloudflare Internal DNS and how does it handle split-horizon DNS? Cloudflare Internal DNS is a generally available service providing authoritative and recursive DNS for private networks on Cloudflare's global network. It handles split-horizon DNS by defining internal and external resolution as separate DNS Views over shared zones, managed from a single control plane, eliminating the need for parallel systems that must be kept in sync manually. _Teams weighing DNS platform consolidation can track releases like this one on daily.dev._ ### What are the main components of Cloudflare Internal DNS and what does each one do? Cloudflare Internal DNS consists of Gateway Resolver, which handles recursive resolution and policy evaluation via a built-in policy engine, and Internal Authoritative DNS, which serves records for internal zones. Customers work with three primary objects: Internal Zones holding private records, DNS Views grouping zones into resolution contexts, and Resolver Policies routing matching queries to a specific view. _Engineers architecting private DNS setups can follow implementation breakdowns like this on daily.dev._ ### How fast do DNS record changes propagate with Cloudflare Internal DNS? Record changes take effect in seconds rather than waiting on TTL expiry. Every change enters through the same DNS Records API whether made via dashboard, Terraform, or direct API call, is persisted in Cloudflare's core data centers for durability, validated, then replicated across the global network with cached entries invalidated as updates arrive. _Ops teams evaluating propagation speed for DNS tooling can compare notes via daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@hra42** · 0 upvotes > it's not available for me sadly. idk what's wrong but okay 🙃 **@trevorsuna** · 0 upvotes > One control plane for public and private DNS sounds handy, especially with Terraform and split-horizon views built in. I’d still want a tested fallback plan before making one provider the front door for every name. **@brennangoewert** · 0 upvotes > im sorry, no. cloud managed internal dns sounds bad to me. if cf api has outages, i'm unable to manage my dns? you'd need a backup for sure, then you are back to managing two planes. ## Similar posts on daily.dev - [Cloudflare Makes Internal DNS Generally Available](https://daily.dev/posts/cloudflare-makes-internal-dns-generally-available-27bt69clt) · InfoQ · 0 upvotes · 0 comments - [DNS is infrastructure. It’s time to manage it that way.](https://daily.dev/posts/dns-is-infrastructure-it-s-time-to-manage-it-that-way--t4fx0zlcn) · The New Stack · 1 upvotes · 0 comments - [Route public traffic to private applications with Cloudflare](https://daily.dev/posts/route-public-traffic-to-private-applications-with-cloudflare-lylocywpg) · Cloudflare · 1 upvotes · 0 comments - [AWS Previews Route 53 Global Resolver to Decouple DNS from Regional Failures](https://daily.dev/posts/aws-previews-route-53-global-resolver-to-decouple-dns-from-regional-failures-i3aosgrjk) · InfoQ · 1 upvotes · 0 comments --- Tags: [#cloudflare](https://daily.dev/tags/cloudflare), [#dns](https://daily.dev/tags/dns) [View this post on daily.dev](https://daily.dev/posts/cloudflare-internal-dns-is-now-generally-available-4o5riyin5) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Cloudflare Internal DNS is now generally available","url":"https://daily.dev/posts/cloudflare-internal-dns-is-now-generally-available-4o5riyin5","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/cloudflare-internal-dns-is-now-generally-available-4o5riyin5"},"datePublished":"2026-07-20T21:01:03.402Z","dateModified":"2026-09-13T20:54:33.376Z","description":"Cloudflare Internal DNS is now generally available for Enterprise customers using Cloudflare Gateway at no additional charge. It unifies public and private DNS...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6469370ee02a834478a589aa387d3185?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6469370ee02a834478a589aa387d3185?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Cloudflare","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Cloudflare","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/38522e1d11354cd6b7af66f9d4316735","url":"https://daily.dev/sources/cloudflare"},"commentCount":3,"discussionUrl":"https://daily.dev/posts/cloudflare-internal-dns-is-now-generally-available-4o5riyin5","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":35},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":3}],"keywords":"cloudflare,dns","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Cloudflare","item":"https://daily.dev/sources/cloudflare"},{"@type":"ListItem","position":3,"name":"Cloudflare Internal DNS is now generally available"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/cloudflare-internal-dns-is-now-generally-available-4o5riyin5","comment":[{"@type":"Comment","text":"it’s not available for me sadly. idk what’s wrong but okay 🙃","datePublished":"2026-07-20T22:29:31.615Z","url":"https://daily.dev/posts/4o5RIYIN5#c-xs5hw2Q3M","author":{"@type":"Person","name":"Henry Rausch","url":"https://daily.dev/hra42","image":"https://avatars.githubusercontent.com/u/44985923?v=4"}},{"@type":"Comment","text":"One control plane for public and private DNS sounds handy, especially with Terraform and split-horizon views built in. I’d still want a tested fallback plan before making one provider the front door for every name.","datePublished":"2026-07-21T02:19:43.436Z","url":"https://daily.dev/posts/4o5RIYIN5#c-eP4jR6K7C","author":{"@type":"Person","name":"Trevor Suna","url":"https://daily.dev/trevorsuna","image":"https://media.daily.dev/image/upload/s--dZ7gXxpp--/f_auto/v1784081551/avatars/avatar_EMoP47rpuw8DNjhp6R1b6?_a=BAMAMicg0"}},{"@type":"Comment","text":"im sorry, no. cloud managed internal dns sounds bad to me. if cf api has outages, i’m unable to manage my dns? you’d need a backup for sure, then you are back to managing two planes.","datePublished":"2026-07-21T13:24:12.972Z","url":"https://daily.dev/posts/4o5RIYIN5#c-q47K82bE4","author":{"@type":"Person","name":"Brennan Goewert","url":"https://daily.dev/brennangoewert","image":"https://avatars.githubusercontent.com/u/15313658?v=4"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/cloudflare-internal-dns-is-now-generally-available-4o5riyin5#faq","mainEntity":[{"@type":"Question","name":"What is Cloudflare Internal DNS and how does it handle split-horizon DNS?","acceptedAnswer":{"@type":"Answer","text":"Cloudflare Internal DNS is a generally available service providing authoritative and recursive DNS for private networks on Cloudflare's global network. It handles split-horizon DNS by defining internal and external resolution as separate DNS Views over shared zones, managed from a single control plane, eliminating the need for parallel systems that must be kept in sync manually. Teams weighing DNS platform consolidation can track releases like this one on daily.dev."}},{"@type":"Question","name":"What are the main components of Cloudflare Internal DNS and what does each one do?","acceptedAnswer":{"@type":"Answer","text":"Cloudflare Internal DNS consists of Gateway Resolver, which handles recursive resolution and policy evaluation via a built-in policy engine, and Internal Authoritative DNS, which serves records for internal zones. Customers work with three primary objects: Internal Zones holding private records, DNS Views grouping zones into resolution contexts, and Resolver Policies routing matching queries to a specific view. Engineers architecting private DNS setups can follow implementation breakdowns like this on daily.dev."}},{"@type":"Question","name":"How fast do DNS record changes propagate with Cloudflare Internal DNS?","acceptedAnswer":{"@type":"Answer","text":"Record changes take effect in seconds rather than waiting on TTL expiry. Every change enters through the same DNS Records API whether made via dashboard, Terraform, or direct API call, is persisted in Cloudflare's core data centers for durability, validated, then replicated across the global network with cached entries invalidated as updates arrive. Ops teams evaluating propagation speed for DNS tooling can compare notes via daily.dev."}}]} ```