API · SDK · runtime · authentication lifecycle intelligence

Last updated · 9 September 2026

SchemaTrace

Breaking changes, enforcement dates and migration requirements.

ST-2026-044 · Enforcement & amendments

Cloudflare removes foundation_dns in favour of nameservers.type

Cloudflare deprecated the foundation_dns boolean for zone DNS settings and account defaults and will stop returning or accepting it during a seven-day rollout beginning 23 November 2026.

Cloudflare DNSfoundation_dnsnameservers.typeAPI removalrollout

Previous state

Clients read and wrote a foundation_dns compatibility boolean.

Current state

Clients must use nameservers.type with cloudflare.advanced or cloudflare.standard; PATCH requests containing foundation_dns will be rejected after rollout.

Who needs to care

DNS automation owners and API clients managing zone or account default nameserver settings.

What to do

Replace the boolean field, map both supported nameserver types and test read and update behaviour before the rollout window.

What the source does not prove

The change concerns API representation and compatibility rather than a Foundation DNS subscription or a forced zone migration. Exact account rollout day varies within the stated seven-day window.

Lifecycle history

Dated event sequence

  1. Change documented

    Cloudflare deprecated the foundation_dns boolean for zone DNS settings and account defaults and will stop returning or accepting it during a seven-day rollout beginning 23 November 2026.

  2. Effective milestone

    Clients must use nameservers.type with cloudflare.advanced or cloudflare.standard; PATCH requests containing foundation_dns will be rejected after rollout.

  3. Transition rollout expected

    Cloudflare plans an earlier seven-day compatibility rollout before the final removal window.

Evidence ledger

First-party sources

  1. 01
    Cloudflare Developers — Cloudflare API deprecations

    Official product documentation or changelog · 2026-07-27

    Open official source ↗