Internal DNS GA for private networks

Internal DNS is now generally available. Internal DNS provides authoritative and recursive DNS for private networks on the same global network and control plane you already use for public DNS, Zero Trust, and application services.

Why it matters

• Consolidate DNS operations. Public and private DNS run on one platform, with one API, one audit trail, and one place to set policy.
• Simplify split-horizon DNS. Internal and external resolution are defined as separate views over shared zones, managed from a single control plane — so there is no drift to chase down.
• Extend Zero Trust to DNS. Resolver policies decide which users and devices resolve against which view, enforced by the same Gateway that already governs the rest of your traffic.

Setting up Internal DNS takes three steps: create a zone, create a view, and define a resolver policy.

<div><div><span>POST /zones</span></div></div><div><div><span>{</span></div></div><div><div><span>  </span><span>"</span><span>account</span><span>"</span><span>:</span><span> </span><span>{</span></div></div><div><div><span>    </span><span>"</span><span>id</span><span>"</span><span>:</span><span> </span><span>"<ACCOUNT_ID>"</span></div></div><div><div><span>  </span><span>},</span></div></div><div><div><span>  </span><span>"</span><span>name</span><span>"</span><span>:</span><span> </span><span>"corp.internal"</span><span>,</span></div></div><div><div><span>  </span><span>"</span><span>type</span><span>"</span><span>:</span><span> </span><span>"internal"</span></div></div><div><div><span>}</span></div></div>

Internal DNS is included with Cloudflare Gateway for Enterprise customers. To get started, refer to the Internal DNS documentation.