Cloudflare changelogs | DNS

DNS - Internal DNS - now in open beta

Tue, 31 Mar 2026 00:00:00 GMT

Internal DNS is now in open beta.

Who can use it?

Internal DNS is bundled as a part of Cloudflare Gateway and is now available to every Enterprise customer with one of the following subscriptions:

Cloudflare Zero Trust Enterprise
Cloudflare Gateway Enterprise

To learn more and get started, refer to the Internal DNS documentation.

DNS - DNS Analytics for Customer Metadata Boundary set to EU region

Fri, 20 Mar 2026 00:00:00 GMT

DNS Analytics is now available for customers with Customer Metadata Boundary (CMB) set to EU. Query your DNS analytics data while keeping metadata stored in the EU region.

This update includes:

DNS Analytics — Access the same DNS analytics experience for zones in CMB=EU accounts.
EU data residency — Analytics data is stored and queried from the EU region, meeting data localization requirements.
DNS Firewall Analytics — DNS Firewall analytics is now supported for CMB=EU customers.

Availability

Available to customers with the Data Localization Suite who have Customer Metadata Boundary configured for the EU region.

Where to find it

Authoritative DNS: In the Cloudflare dashboard, select your zone and go to the Analytics page.
Go to Analytics
DNS Firewall: In the Cloudflare dashboard, go to the DNS Firewall Analytics page.
Go to Analytics

For more information, refer to DNS Analytics and DNS Firewall Analytics.

DNS - DNS Firewall Analytics — now in the Cloudflare dashboard

Tue, 16 Sep 2025 00:00:00 GMT

What's New

Access GraphQL-powered DNS Firewall analytics directly in the Cloudflare dashboard.

Explore Four Interactive Panels

Query summary: Describes trends over time, segmented by dimensions.
Query statistics: Describes totals, cached/uncached queries, and processing/response times.
DNS queries by data center: Describes global view and the top 10 data centers.
Top query statistics: Shows a breakdown by key dimensions, with search and expand options (up to top 100 items).

Additional features:

Apply filters and time ranges once. Changes reflect across all panels.
Filter by dimensions like query name, query type, cluster, data center, protocol (UDP/TCP), IP version, response code/reason, and more.
Access up to 62 days of historical data with flexible intervals.

Availability

Available to all DNS Firewall customers as part of their existing subscription.

Where to Find It

In the Cloudflare dashboard, go to the DNS Firewall page.
Go to Analytics
Refer to the DNS Firewall Analytics to learn more.

DNS - Account-level DNS analytics now available via GraphQL Analytics API

Thu, 19 Jun 2025 00:00:00 GMT

Authoritative DNS analytics are now available on the account level via the Cloudflare GraphQL Analytics API.

This allows users to query DNS analytics across multiple zones in their account, by using the accounts filter.

Here is an example to retrieve the most recent DNS queries across all zones in your account that resulted in an NXDOMAIN response over a given time frame. Please replace a30f822fcd7c401984bf85d8f2a5111c with your actual account ID.

query GetLatestNXDOMAINResponses {
  viewer {
    accounts(filter: { accountTag: "a30f822fcd7c401984bf85d8f2a5111c" }) {
      dnsAnalyticsAdaptive(
        filter: {
          date_geq: "2025-06-16"
          date_leq: "2025-06-18"
          responseCode: "NXDOMAIN"
        }
        limit: 10000
        orderBy: [datetime_DESC]
      ) {
        zoneTag
        queryName
        responseCode
        queryType
        datetime
      }
    }
  }
}

Run in GraphQL API Explorer

To learn more and get started, refer to the DNS Analytics documentation.

DNS - Internal DNS (beta) now manageable in the Cloudflare dashboard

Mon, 16 Jun 2025 00:00:00 GMT

Participating beta testers can now fully configure Internal DNS directly in the Cloudflare dashboard.

Internal DNS enables customers to:

Map internal hostnames to private IPs for services, devices, and applications not exposed to the public Internet
Resolve internal DNS queries securely through Cloudflare Gateway
Use split-horizon DNS to return different responses based on network context
Consolidate internal and public DNS zones within a single management platform

What’s new in this release:

Beta participants can now create and manage internal zones and views in the Cloudflare dashboard

To learn more and get started, refer to the Internal DNS documentation.

DNS - NSEC3 support for DNSSEC

Wed, 11 Jun 2025 00:00:00 GMT

Enterprise customers can now select NSEC3 as method for proof of non-existence on their zones.

What's new:

NSEC3 support for live-signed zones – For both primary and secondary zones that are configured to be live-signed (also known as "on-the-fly signing"), NSEC3 can now be selected as proof of non-existence.
NSEC3 support for pre-signed zones – Secondary zones that are transferred to Cloudflare in a pre-signed setup now also support NSEC3 as proof of non-existence.

For more information and how to enable NSEC3, refer to the NSEC3 documentation.

DNS - Improved onboarding for Shopify merchants

Tue, 03 Jun 2025 00:00:00 GMT

Shopify merchants can now onboard to O2O automatically, without needing to contact support or community members.

What's new:

Automatic enablement – O2O is available for all mutual Cloudflare and Shopify customers.
Branded record display – Merchants see a Shopify logo in DNS records, complete with helpful tooltips.
Checkout protection – Workers and Snippets are blocked from running on the checkout path to reduce risk and improve security.

For more information, refer to the provider guide.

DNS - Removed unused meta fields from DNS records

Sun, 02 Feb 2025 00:00:00 GMT

Cloudflare is removing five fields from the meta object of DNS records. These fields have been unused for more than a year and are no longer set on new records. This change may take up to four weeks to fully roll out.

The affected fields are:

the auto_added boolean
the managed_by_apps boolean and corresponding apps_install_id
the managed_by_argo_tunnel boolean and corresponding argo_tunnel_id

An example record returned from the API would now look like the following:

{
  "result": {
    "id": "<ID>",
    "zone_id": "<ZONE_ID>",
    "zone_name": "example.com",
    "name": "www.example.com",
    "type": "A",
    "content": "192.0.2.1",
    "proxiable": true,
    "proxied": false,
    "ttl": 1,
    "locked": false,
    "meta": {
      "auto_added": false,
      "managed_by_apps": false,
      "managed_by_argo_tunnel": false,
      "source": "primary"
    },
    "comment": null,
    "tags": [],
    "created_on": "2025-03-17T20:37:05.368097Z",
    "modified_on": "2025-03-17T20:37:05.368097Z"
  },
  "success": true,
  "errors": [],
  "messages": []
}

For more guidance, refer to Manage DNS records.