Skip to content

Add deprecation to DNS Records API - Remove eligible zones for custom nameservers endpoint #18840

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 19, 2024
Merged

Add deprecation to DNS Records API - Remove eligible zones for custom nameservers endpoint #18840

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions src/content/changelogs/api-deprecations.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,16 @@ productLink: "/fundamentals/"
productArea: Core platform
productAreaLink: /fundamentals/reference/changelog/platform/
entries:
- publish_date: "2025-03-23"
title: "Eligible Zones For Account Custom Nameservers"
description: |-
Deprecation date: March 23, 2025

Users can now add custom nameservers that are not part of a zone managed within their account. As a result, any zone is eligible for custom nameservers, regardless of whether it is managed by Cloudflare. Given this change, an endpoint to check for eligible zones is no longer relevant and is therefore being deprecated.

Deprecated APIs:
- `GET /accounts/:account_id/custom_ns/availability`

- publish_date: "2024-12-09"
title: "Access applications: self_hosted_domains"
description: |-
Expand Down
Loading