Skip to content

Commit a105c7d

Browse files
committed
Clarifying CIDR block usage for Address Maps in MT w/ L7 guide - add note for prefix delegations
1 parent 845a982 commit a105c7d

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ sidebar:
77

88
---
99

10-
import { Details, Example, TabItem, Tabs, GlossaryTooltip } from "~/components";
10+
import { Details, Example, TabItem, Tabs, GlossaryTooltip, Aside} from "~/components";
1111

1212
[Magic Transit](/magic-transit/) customers using BYOIP can also benefit from the performance, reliability, and security that Cloudflare offers for HTTP-based applications.
1313

@@ -40,8 +40,11 @@ Even though it is possible to add discrete bindings for non-contiguous CIDR bloc
4040

4141
</Details>
4242

43-
Once a service binding is created (or deleted), it will take four to six hours to propagate across Cloudflare's global network. Services for the IP addresses in scope will likely be disrupted during this window.
43+
Once a service binding is created (or deleted), it will take **four** to **six** hours to propagate across Cloudflare's global network. Services for the IP addresses in scope will likely be disrupted during this window.
4444

45+
:::note
46+
This assumes that the prefix is tied to an account that has both Magic Transit and CDN properties. If not refer to [Prefix Delegations](/byoip/concepts/prefix-delegations/). The [Edge Service Bindings](#2-create-service-binding) will need to be done on the parent account as well.
47+
:::
4548

4649
## 1. Get account information
4750

@@ -199,9 +202,9 @@ At this point, if an address map for a zone `example.com` specifies that Cloudfl
199202
4. As the HTTP response egresses the Cloudflare network back to the client side, the source IP address of the response becomes `203.0.113.100` (the IP address that the HTTP request originally landed on).
200203

201204
</Details>
202-
205+
:::note
203206
Having the same IP address as ingress IP (defined in the address map) and origin IP (listed in the DNS record) will not cause any loops.
204-
207+
:::
205208
<Details header="Example" >
206209

207210
Assuming `203.0.113.100` was also the origin IP, the DNS record would look like the following:

0 commit comments

Comments
 (0)