Skip to content

Commit 933987a

Browse files
kodster28kodster28
authored
[Chore 2] Add product param explicitly to Render (#24569)
1 parent ac6caf7 commit 933987a

File tree

281 files changed

+2170
-2304
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

281 files changed

+2170
-2304
lines changed

‎src/content/docs/dns/cname-flattening/index.mdx‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sidebar:
66
label: About
77
---
88

9-
import { Render, GlossaryTooltip } from "~/components"
9+
import { Render, GlossaryTooltip } from "~/components";
1010

1111
CNAME flattening speeds up CNAME resolution and allows you to use a CNAME record at your <GlossaryTooltip term="zone apex" link="/dns/concepts/#zone-apex">zone apex</GlossaryTooltip> (`example.com`).
1212

@@ -26,5 +26,5 @@ For information about CNAME flattening in [Internal DNS](/dns/internal-dns/), re
2626

2727
## Aspects to keep in mind
2828

29-
* CNAME flattening happens by default in some cases. Refer to [Setup](/dns/cname-flattening/set-up-cname-flattening/) for details.
30-
* <Render file="cname-flattening-callout" />
29+
- CNAME flattening happens by default in some cases. Refer to [Setup](/dns/cname-flattening/set-up-cname-flattening/) for details.
30+
- <Render file="cname-flattening-callout" product="dns" />

‎src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx‎

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,17 +6,14 @@ sidebar:
66
head:
77
- tag: title
88
content: Set up CNAME flattening
9-
109
---
1110

12-
import { Render, TabItem, Tabs, GlossaryTooltip } from "~/components"
11+
import { Render, TabItem, Tabs, GlossaryTooltip } from "~/components";
1312

1413
:::note
1514

16-
1715
If the CNAME target is on the same zone as the CNAME record, Cloudflare proceeds with CNAME flattening and ignores the **CNAME Flattening** setting.
1816

19-
2017
:::
2118

2219
## For your zone apex
@@ -40,7 +37,8 @@ Make a `PATCH` request to the [Update DNS Settings](/api/resources/dns/subresour
4037
</TabItem> </Tabs>
4138

4239
:::caution
43-
<Render file="cname-flattening-callout" />
40+
41+
<Render file="cname-flattening-callout" product="dns" />
4442
:::
4543

4644
## Per record
@@ -59,10 +57,11 @@ If you use this option, a special [tag](/dns/manage-dns-records/reference/record
5957

6058
:::note[Unavailable flatten option]
6159
For the following cases, **Flatten** will not be available:
60+
6261
- The record is at the [zone apex](#for-your-zone-apex).
6362
- The record is already proxied, which means it will be flattened by default.
6463
- **CNAME flattening for all CNAME records** is turned on, which means you cannot override it per record.
65-
:::
64+
:::
6665

6766
</TabItem> <TabItem label="API">
6867

‎src/content/docs/dns/dns-firewall/random-prefix-attacks/about.mdx‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@ head:
1010
description: Learn about random prefix attacks. As part of DNS Firewall, Cloudflare can protect your upstream authoritative nameservers from these attacks.
1111
---
1212

13-
import { Render } from "~/components"
13+
import { Render } from "~/components";
1414

15-
<Render file="random-prefix-attack-definition" /> <br/>
15+
<Render file="random-prefix-attack-definition" product="dns" /> <br />
1616

1717
## Attack characteristics
1818

@@ -30,7 +30,7 @@ If the request only involved nonexistent domains, the `NXDOMAIN` errors would on
3030
D[Authoritative NS]
3131
```
3232

33-
<br/>
33+
<br />
3434

3535
### Queries for nonexistent subdomains
3636

@@ -47,7 +47,7 @@ These attacks are successful because they target subdomains, which require a res
4747
B --"6)" <code>NXDOMAIN error</code>--> A
4848
```
4949

50-
<br/>
50+
<br />
5151

5252
With an attack against a subdomain of an existing domain, the resolver is forced to fully resolve it against the authoritative nameservers since these random subdomains are likely not cached by the resolver or any other proxy. If an attacker sends enough of these queries, and the authoritative nameservers cannot handle the query load, it will become unresponsive or even fall over, taking all zones it is hosting down, not just the attacked zone.
5353

‎src/content/docs/dns/dns-firewall/random-prefix-attacks/index.mdx‎

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,19 +3,18 @@ pcx_content_type: concept
33
title: Random prefix attack mitigation
44
sidebar:
55
order: 4
6-
76
---
87

9-
import { Render } from "~/components"
8+
import { Render } from "~/components";
109

11-
<Render file="random-prefix-attack-definition" />
10+
<Render file="random-prefix-attack-definition" product="dns" />
1211

1312
As part of [DNS Firewall](/dns/dns-firewall/), Cloudflare can protect your upstream authoritative nameservers from these attacks by blocking DNS queries that are determined to be part of an attack and thus preventing them from reaching your authoritative nameservers, where they could cause harm by overloading resources. This protection is an opt-in feature because of the potential for false positives.
1413

1514
## Resources
1615

17-
* [Background information](/dns/dns-firewall/random-prefix-attacks/about/)
18-
* [Setup](/dns/dns-firewall/random-prefix-attacks/setup/)
16+
- [Background information](/dns/dns-firewall/random-prefix-attacks/about/)
17+
- [Setup](/dns/dns-firewall/random-prefix-attacks/setup/)
1918

2019
## Limitations
2120

‎src/content/docs/dns/foundation-dns/advanced-nameservers.mdx‎

Lines changed: 12 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -3,27 +3,27 @@ pcx_content_type: concept
33
title: Advanced nameservers
44
sidebar:
55
order: 2
6-
76
---
87

9-
import { Details, GlossaryTooltip, Render } from "~/components"
8+
import { Details, GlossaryTooltip, Render } from "~/components";
109

1110
Advanced nameservers included with [Foundation DNS](/dns/foundation-dns/) offer improved resiliency and more consistent nameserver assignment.
1211

1312
Consider the sections below for details about advanced nameservers, and refer to [Set up advanced nameservers](/dns/foundation-dns/setup/) to learn how to enable this feature.
1413

1514
:::note
16-
<Render file="ns-advanced-vs-custom" />
17-
Also, [some behaviors are different](/dns/foundation-dns/setup/#differences-from-standard-nameservers) when compared to standard nameservers.
18-
:::
15+
16+
<Render file="ns-advanced-vs-custom" product="dns" />
17+
Also, [some behaviors are
18+
different](/dns/foundation-dns/setup/#differences-from-standard-nameservers)
19+
when compared to standard nameservers. :::
1920

2021
## Anycast network groups
2122

2223
To increase resiliency, advanced nameserver IPs are advertised by only one of two <GlossaryTooltip term="anycast">anycast</GlossaryTooltip> network groups.
2324

2425
The two groups consist of data centers that are geographically equally distributed.
2526

26-
2727
<Details header="United Kingdom example">
2828

2929
| IPs | Group | Data centers |
@@ -32,7 +32,6 @@ The two groups consist of data centers that are geographically equally distribut
3232
| `172.64.40.1` | B | Manchester |
3333
| `162.159.60.1` | A | London and Edinburgh |
3434

35-
3635
</Details>
3736

3837
In DNS resolution, a resolver eventually acquires a list of all IPs where authoritative nameservers for a domain can be reached, and will then usually prefer the IP with the best resolution performance.
@@ -51,22 +50,20 @@ The dedicated release process means that only changes that have been in producti
5150

5251
While standard Cloudflare nameservers are hosted under `ns.cloudflare.com` or `secondary.cloudflare.com`, advanced nameservers use different domains:
5352

54-
* `foundationdns.com`
55-
* `foundationdns.net`
56-
* `foundationdns.org`
53+
- `foundationdns.com`
54+
- `foundationdns.net`
55+
- `foundationdns.org`
5756

5857
Using the different TLDs (`.com`, `.net`, and `.org`) and making these available only to enterprise accounts allows for better predictability and consistency in nameserver assignment.
5958

6059
There should also be less conflicts when guaranteeing that directly descending zones do not have the same nameserver set.
6160

62-
6361
<Details header="Descending zones example">
6462

6563
Consider the domain `example.com`, and subdomains `abc.example.com` and `123.example.com`:
6664

67-
* `abc.example.com` and `123.example.com` directly descend from `example.com` and cannot have the same nameservers as `example.com`.
68-
* `abc.example.com` and `123.example.com` are sibling domains and can have the same nameservers.
69-
* `new.abc.example.com` directly descends from both `abc.example.com` and `example.com`, and cannot have the same nameservers as them, but can have the same nameservers as `123.example.com`.
70-
65+
- `abc.example.com` and `123.example.com` directly descend from `example.com` and cannot have the same nameservers as `example.com`.
66+
- `abc.example.com` and `123.example.com` are sibling domains and can have the same nameservers.
67+
- `new.abc.example.com` directly descends from both `abc.example.com` and `example.com`, and cannot have the same nameservers as them, but can have the same nameservers as `123.example.com`.
7168

7269
</Details>

‎src/content/docs/dns/foundation-dns/setup.mdx‎

Lines changed: 34 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -6,36 +6,41 @@ sidebar:
66
label: Setup
77
---
88

9-
import { TabItem, Tabs, APIRequest, Render, Details, Example } from "~/components";
9+
import {
10+
TabItem,
11+
Tabs,
12+
APIRequest,
13+
Render,
14+
Details,
15+
Example,
16+
} from "~/components";
1017

1118
Advanced nameservers included with [Foundation DNS](/dns/foundation-dns/) are an opt-in configuration.
1219

13-
1420
## Before you begin
1521

1622
Before opting in for advanced nameservers, consider the following:
1723

18-
- <Render file="ns-advanced-vs-custom" />
24+
- <Render file="ns-advanced-vs-custom" product="dns" />
1925

2026
### Differences from standard nameservers
2127

2228
Some behaviors are different from standard Cloudflare nameservers:
29+
2330
- Wildcard records: if moving from standard Cloudflare nameservers to Foundation DNS advanced nameservers, make sure to explicitly create records for subdomains currently covered by wildcard records (`*.example.com`).
2431
- Subdomain delegation: once a subdomain is delegated via NS records, Cloudflare will not serve any other records (such as A, TXT, or CNAME) on that subdomain from the parent zone, even if those records exist.
2532

2633
<Details header="Example">
2734

2835
<Example>
29-
DNS management for **example.com**
30-
| **Type** | **Name** | **Content** |
31-
| -------- | -------- | ------------------------- |
32-
| NS | www | ns1.externalhost.com |
33-
| NS | www | ns2.externalhost.com |
34-
| TXT | www | "5bb16e6b5a444eedb48ace40c471bcc9" |
35-
| A | www | `192.0.2.1` |
36+
DNS management for **example.com** | **Type** | **Name** | **Content** | |
37+
-------- | -------- | ------------------------- | | NS | www |
38+
ns1.externalhost.com | | NS | www | ns2.externalhost.com | | TXT | www |
39+
"5bb16e6b5a444eedb48ace40c471bcc9" | | A | www | `192.0.2.1` |
3640
</Example>
3741

3842
In this example, the TXT record and the A record for `www.example.com` will not be served.
43+
3944
</Details>
4045

4146
## Enable on a zone
@@ -44,34 +49,33 @@ To enable advanced nameservers on an existing zone:
4449

4550
1. Opt for advanced nameservers on your zone:
4651

47-
<Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
48-
49-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.
50-
2. Go to **DNS** > **Records**.
51-
3. In the **Cloudflare nameservers** card, enable **Advanced nameservers**.
52-
4. After you refresh the page, the card will display the values for your advanced nameservers `NS` records.
52+
<Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
53+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.
54+
2. Go to **DNS** > **Records**.
55+
3. In the **Cloudflare nameservers** card, enable **Advanced nameservers**.
56+
4. After you refresh the page, the card will display the values for your advanced nameservers `NS` records.
5357

54-
</TabItem> <TabItem label="API">
58+
</TabItem> <TabItem label="API">
5559

56-
Use the [Update DNS Settings](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) endpoint to send a PATCH request like the following:
60+
Use the [Update DNS Settings](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) endpoint to send a PATCH request like the following:
5761

58-
<APIRequest
59-
path="/zones/{zone_id}/dns_settings"
60-
method="PATCH"
61-
json={{
62-
"foundation_dns": true,
63-
}}
64-
/>
62+
<APIRequest
63+
path="/zones/{zone_id}/dns_settings"
64+
method="PATCH"
65+
json={{
66+
foundation_dns: true,
67+
}}
68+
/>
6569

66-
The response body will contain your assigned namservers in the `nameservers` object. You will use these nameservers in the next step.
70+
The response body will contain your assigned namservers in the `nameservers` object. You will use these nameservers in the next step.
6771

68-
</TabItem> </Tabs>
72+
</TabItem> </Tabs>
6973

7074
2. Update the authoritative nameservers at your registrar. This step depends on whether you are using [Cloudflare Registrar](/registrar/):
7175
- If you are using Cloudflare Registrar, [contact Cloudflare Support](/support/contacting-cloudflare-support/) to have your nameservers updated.
7276
- If you are using a different registrar or if your zone is delegated to a parent zone, [manually update your nameservers](/dns/nameservers/update-nameservers/#specific-processes).
7377

74-
:::caution
78+
:::caution
7579

76-
Make sure the values for your assigned nameservers are copied exactly.
77-
:::
80+
Make sure the values for your assigned nameservers are copied exactly.
81+
:::

‎src/content/docs/dns/internal-dns/dns-views.mdx‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,13 @@ Refer to the sections below for details on how to manage your DNS views, or cons
1616

1717
When setting up DNS views, observe the following conditions:
1818

19-
<Render file="internal-dns-view-conditions" />
19+
<Render file="internal-dns-view-conditions" product="dns" />
2020

2121
## Create a view
2222

2323
<Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
2424

25-
<Render file="internal-dns-view-create-dash"/>
25+
<Render file="internal-dns-view-create-dash" />
2626

2727
</TabItem>
2828
<TabItem label="API">
@@ -42,7 +42,7 @@ It is also possible to delete a DNS view that is being referenced by a Gateway r
4242
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
4343
2. Go to **Internal DNS** > **Views**.
4444
3. Find the view you want to delete.
45-
4. Select the three dots in the corresponding row and choose *Delete*.
45+
4. Select the three dots in the corresponding row and choose _Delete_.
4646
5. In the confirmation dialog, select **Delete** again to proceed.
4747

4848
</TabItem>
@@ -56,4 +56,4 @@ Use the [Delete Internal DNS View](/api/resources/dns/subresources/settings/subr
5656

5757
- [Update a DNS view](/api/resources/dns/subresources/settings/subresources/account/subresources/views/methods/edit/) (`PATCH`)
5858
- [Get view details](/api/resources/dns/subresources/settings/subresources/account/subresources/views/methods/get/) (`GET`)
59-
- [List DNS views](/api/resources/dns/subresources/settings/subresources/account/subresources/views/methods/list/) (`GET`)
59+
- [List DNS views](/api/resources/dns/subresources/settings/subresources/account/subresources/views/methods/list/) (`GET`)

0 commit comments

Comments
 (0)