Skip to content

Commit 415168b

Browse files
[DNS] Remove outdated domains list screenshot (#16794)
* Fix notes from DNS tile that ended up 'undefined' after migration * Remove outdated image and replace by written description
1 parent 19c1476 commit 415168b

File tree

4 files changed

+8
-10
lines changed

4 files changed

+8
-10
lines changed
-79.3 KB
Binary file not shown.

src/content/docs/dns/nameservers/custom-nameservers/tenant-custom-nameservers.mdx

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,10 +45,11 @@ curl --request PUT https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_n
4545
}'
4646
```
4747

48-
:::undefined
48+
:::note
4949

5050
If the parameter `ns_type` is omitted, the default type `account` will be assigned.
51-
If the parameter `ns_set` is omitted, the default set `1` will be assigned.
51+
52+
If the parameter `ns_set` is omitted, the default set `1` will be assigned.
5253
:::
5354

5455
2. If you are **not** using [Cloudflare Registrar](/registrar/), update the nameservers at your registrar to use the TCNS names. If you are using [Cloudflare Registrar](/registrar/), no further action is needed.

src/content/docs/dns/zone-setups/subdomain-setup/index.mdx

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,12 @@ sidebar:
88

99
import { DirectoryListing, FeatureTable, GlossaryTooltip } from "~/components"
1010

11-
When you use a subdomain setup, you can manage the [Cloudflare configurations](/fundamentals/concepts/how-cloudflare-works/) for one or more subdomains separately from those associated with your <GlossaryTooltip term="apex domain">apex domain</GlossaryTooltip>.
11+
When you use a subdomain setup, you can manage the [Cloudflare configurations](/fundamentals/concepts/how-cloudflare-works/) for one or more subdomains separately from those associated with your <GlossaryTooltip term="apex domain">apex domain</GlossaryTooltip>. This means that, on your [account homepage](https://dash.cloudflare.com/?to=/:account/), you would find websites like `example.com` or `blog.example.com` listed as separate <GlossaryTooltip term="DNS zone">zones</GlossaryTooltip>.
1212

13-
:::undefined
14-
15-
This is different from simply creating a subdomain for a site you already have in Cloudflare. If you do not need separate Cloudflare configuration for your subdomain, refer to [Create a subdomain record](/dns/manage-dns-records/how-to/create-subdomain/).
13+
:::note
14+
This is different from simply creating a subdomain for a site you already have in Cloudflare. If you do not need separate Cloudflare configuration for your subdomain, refer to [Create a subdomain record](/dns/manage-dns-records/how-to/create-subdomain/).
1615
:::
1716

18-
![Screenshot showing a zone with a parent domain and a child subdomain](~/assets/images/dns/subdomain-zone.png)
19-
2017
You might use this setup when you want to share access to a specific subdomain's settings with different teams, but have stricter controls on your apex domain. For example, a subdomain setup could allow your documentation team to manage the Cloudflare configuration for `docs.example.com`, while preventing them from adjusting any settings on `example.com`.
2118

2219
Subdomain setups are also useful when different subdomains require entirely different settings. For example, you may have different requirements for `docs.example.com`, `blog.example.com`, and `community.example.com`.

src/content/partials/dns/acns-tcns-byoip.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ inputParameters: param1;;param2
55

66
import { Markdown } from "~/components"
77

8-
:::undefined
8+
:::note
99

10-
{props.one} owners that want to [use their own IP prefix](/byoip/) for the {props.two} custom nameservers should contact their account team.
10+
{props.one} owners that want to [use their own IP prefix](/byoip/) for the {props.two} custom nameservers should contact their account team.
1111
:::

0 commit comments

Comments
 (0)