Cloudflare retires the foundation_dns flag for a nameserver type field
The DNS settings API starts returning nameservers.type instead of a boolean on 26 October, and drops the old foundation_dns field entirely on 23 November.
Cloudflare started rolling out a change to its DNS settings API today, 26 October, replacing the foundation_dns boolean with a nameservers.type field set to "cloudflare.advanced" or "cloudflare.standard". The rollout to the PATCH /zones/{zone_id}/dns_settings and PATCH /accounts/{account_id}/dns_settings endpoints is expected to take about seven days to reach every account.
foundation_dns stays readable and writable as a compatibility alias during the transition, but a request that sets both fields to conflicting values is rejected. The old field is deprecated as of 27 July and reaches end of life on 23 November, after which the API stops accepting or returning it at all.
PATCH /zones/{zone_id}/dns_settings
{ "nameservers": { "type": "cloudflare.advanced" } }Why it matters: anyone managing DNS through Terraform, Pulumi, or a custom script that sets foundation_dns directly has until 23 November to switch to nameservers.type, or those API calls start failing. It’s a narrow change, but a deadline worth putting on the calendar if your infrastructure code touches Cloudflare’s DNS settings endpoints.