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

Author: matilde-cf

src/content/changelogs/api-deprecations.yaml

@@ -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: |-
@@ -24,8 +34,8 @@ entries:
       ```json
       {
         // ...
-        "destinations": [
           {
+        "destinations": [
             "type": "public",
             "uri": "foo.example.com"
           },
@@ -170,27 +180,27 @@ entries:
 
       The following URL parameters for filtering DNS records are deprecated:
 
-      - `name=contains:value`  
+      - `name=contains:value  `
         Instead, use the supported `name.contains=value` syntax.
-      - `name=starts_with:value`  
+      - `name=starts_with:value  `
         Instead, use the supported `name.startswith=value` syntax.
-      - `name=ends_with:value`  
+      - `name=ends_with:value  `
         Instead, use the supported `name.endswith=value` syntax.
-      - `name=one,two,three` (searching for one of multiple possible names, separated by commas)  
+      - `name=one,two,three` (searching for one of multiple possible names, separated by commas)
         Instead, make multiple requests, one for each possible `name`.
         Alternatively, if only querying the `name` field, the `?match=any&name=one&name=two&name=three` syntax can be used instead.
         This syntax has an extended deprecation date of May 23, 2025.
-      - `content=contains:value`  
+      - `content=contains:value  `
         Instead, use the supported `content.contains=value` syntax.
-      - `content=starts_with:value`  
+      - `content=starts_with:value  `
         Instead, use the supported `content.startswith=value` syntax.
-      - `content=ends_with:value`  
+      - `content=ends_with:value  `
         Instead, use the supported `content.endswith=value` syntax.
-      - `content=one,two,three` (searching for one of multiple possible contents, separated by commas)  
+      - `content=one,two,three` (searching for one of multiple possible contents, separated by commas)
         Instead, make multiple requests, one for each possible `content`.
         Alternatively, if only querying the `content` field, the `?match=any&content=one&content=two&content=three` syntax can be used instead.
         This syntax has an extended deprecation date of May 23, 2025.
-      - `type=contains:value`  
+      - `type=contains:value  `
         Searching for substrings of a type name will no longer be supported.
         Instead, please search for an exact type name, such as `type=CNAME`.
         If the input value is a free-text search from a human user, consider using the `search` parameter instead.
@@ -566,4 +576,4 @@ entries:
       - `GET organizations/:organization_identifier/railguns/:identifier/zones`
 
       Replacement:
-      Accounts API
+      Accounts API