Skip to content

Commit e021ee9

Browse files
Add WIP note to work depending on API docs or tabled for later
1 parent 204a055 commit e021ee9

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/content/docs/byoip/get-started.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ The exact steps to update your IRR record will depend on the registry you are us
9797
9898
1. Consider the size of the prefix you are bringing to Cloudflare. Since the standard `in-addr.arpa` tree assumes delegations on octet or nibble boundaries, if you onboard prefixes that are not aligned with those, you will have to split up the prefix into subnets and create the corresponding reverse DNS zones for each.
9999
100-
(Add calculation examples (collapsable))
100+
(WIP - Add calculation examples (collapsable))
101101
102102
2. Set up a reverse DNS zone. If you use Cloudflare for DNS, refer to [Reverse DNS zones](/dns/additional-options/reverse-zones/#set-up-a-reverse-zone). If you use a different DNS provider, follow their instructions.
103103
3. Create TXT records using `cf-validation` as their `name`. They should look like the following example:
@@ -117,9 +117,9 @@ Once the ownership validation is successful, and if the RPKI and IRR validations
117117
3. (Optional) Use the [Prefix Details endpoint](/api/resources/addressing/subresources/prefixes/methods/get/) to check if any issues were found during validation. If so, proceed with the necessary changes and make a request to restart validation.
118118
<APIRequest path= "/accounts/{account_id}/addressing/prefixes/{prefix_id}" method="GET" />
119119
120-
(Add response example (collapsable))
120+
(WIP - Add response example (collapsable))
121121
122-
(Add code block example)
122+
(WIP - Add code block example)
123123
124124
4. (Optional) You can allow other accounts to use part or all of your BYOIP prefix. Refer to [Prefix delegations](/byoip/concepts/prefix-delegations/) for details.
125125
@@ -171,7 +171,7 @@ The steps below only cover assigning specific IPs to additional services. For gu
171171
172172
1. Plan for what IP(s) will get the additional binding. Cloudflare **strongly** recommends implementing service bindings through an **aggregated** CIDR block, as it is more efficient than adding discrete bindings for non-contiguous CIDR blocks.
173173
174-
(Add collapsable example similar to existing ones in the service bindings docs)
174+
(WIP - Add collapsable example similar to existing ones in the service bindings docs)
175175
176176
2. Make a `POST` request to the [Create service binding](/api/resources/addressing/subresources/prefixes/subresources/service_bindings/methods/create/) endpoint, indicating the IP address you want to bind to the CDN or Spectrum. Specify the **corresponding network mask** as needed.
177177

0 commit comments

Comments
 (0)