From 6fceb857eb3df035c00fa63fb4b4341b83007381 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Thu, 4 Sep 2025 08:58:56 +0100 Subject: [PATCH 1/3] Replace Account Settings page occurrences --- .../additional-options/dns-zone-defaults.mdx | 9 ++++++-- .../account-custom-nameservers.mdx | 23 +++++++++++++------ .../access-control-lists/create-new-list.mdx | 16 +++++++------ .../cloudflare-as-primary/setup.mdx | 16 +++++++------ .../dns/zone-setups/zone-transfers/index.mdx | 10 ++++++-- 5 files changed, 49 insertions(+), 25 deletions(-) diff --git a/src/content/docs/dns/additional-options/dns-zone-defaults.mdx b/src/content/docs/dns/additional-options/dns-zone-defaults.mdx index be257d7c1eea4ff..03f7f712f2cac49 100644 --- a/src/content/docs/dns/additional-options/dns-zone-defaults.mdx +++ b/src/content/docs/dns/additional-options/dns-zone-defaults.mdx @@ -6,6 +6,8 @@ sidebar: label: Zone defaults --- +import { DashButton } from "~/components"; + While there are default values for DNS settings that Cloudflare applies to all new zones, Enterprise accounts have the option to configure their own DNS zone defaults according to their preference. :::caution @@ -14,8 +16,11 @@ DNS zone defaults are only applied at the moment a new zone is created and will ## Steps -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account. -2. Go to **Manage Account** > **Configurations** > **DNS Settings**. If these options are not displayed on your Cloudflare dashboard, you may need to reach out to your account team to have them added. +1. In the Cloudflare dashboard, go to the account **Settings** page. + + + +2. Go to **DNS Settings**. If these options are not displayed on your Cloudflare dashboard, you may need to reach out to your account team to have them added. 3. For **DNS zone defaults**, select **Configure defaults**. The values you select for the listed settings will be automatically applied to new zones as you add them to your Cloudflare account. diff --git a/src/content/docs/dns/nameservers/custom-nameservers/account-custom-nameservers.mdx b/src/content/docs/dns/nameservers/custom-nameservers/account-custom-nameservers.mdx index fb69ce1447a27fc..fdc607537bac81a 100644 --- a/src/content/docs/dns/nameservers/custom-nameservers/account-custom-nameservers.mdx +++ b/src/content/docs/dns/nameservers/custom-nameservers/account-custom-nameservers.mdx @@ -12,7 +12,7 @@ description: With account-level custom nameservers, you can use the same custom provide the nameservers names do not have to exist as zones in Cloudflare. --- -import { Example, Render, Tabs, TabItem } from "~/components"; +import { Example, Render, Tabs, TabItem, DashButton } from "~/components"; -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account. -2. Go to **Manage Account** > **Configurations** > **DNS Settings**. +1. In the Cloudflare dashboard, go to the account **Settings** page. + + + +2. Go to **DNS Settings**. 3. For **Account custom nameservers**, select **Configure custom nameservers**. 4. Insert a fully qualified domain name for **Nameserver name** and choose a **Nameserver set**. Follow the [configuration conditions](#configuration-conditions). @@ -131,8 +134,11 @@ To make ACNS the default option for all new zones added to your account from now -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account. -2. Go to **Manage Account** > **Configurations**. +1. In the Cloudflare dashboard, go to the account **Settings** page. + + + +2. Go to **DNS Settings**. 3. For **DNS zone defaults**, select **Configure defaults**. 4. Change the **Nameserver assignment method** to **Account custom nameservers**. @@ -182,8 +188,11 @@ Following the [configuration conditions](#configuration-conditions), each set mu -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account. -2. Go to **Manage Account** > **Configurations** > **DNS Settings**. +1. In the Cloudflare dashboard, go to the account **Settings** page. + + + +2. Go to **DNS Settings**. 3. For **Account custom nameservers**, select **Delete** next to the ACNS name. diff --git a/src/content/docs/dns/zone-setups/zone-transfers/access-control-lists/create-new-list.mdx b/src/content/docs/dns/zone-setups/zone-transfers/access-control-lists/create-new-list.mdx index 352c8fef49b2f84..e3e02dd0caa477c 100644 --- a/src/content/docs/dns/zone-setups/zone-transfers/access-control-lists/create-new-list.mdx +++ b/src/content/docs/dns/zone-setups/zone-transfers/access-control-lists/create-new-list.mdx @@ -8,7 +8,7 @@ head: content: Create a new Access Control List --- -import { TabItem, Tabs } from "~/components"; +import { TabItem, Tabs, DashButton } from "~/components"; You need to create an Access Control List (ACL) if Cloudflare is your [secondary DNS provider](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/). The ACL will specify additional NOTIFY IPs that Cloudflare should listen to. @@ -18,14 +18,16 @@ An ACL is configured at the account level, which means that it will apply to eve To create a new ACL using the dashboard: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. -2. Go to **Manage Account** > **Configurations**. -3. Go to **DNS Zone Transfers**. -4. For **ACL**, click **Create**. -5. Enter the following information: +1. In the Cloudflare dashboard, go to the account **Settings** page. + + + +2. Go to **DNS Settings**. +3. Under **DNS Zone Transfers**, for **ACL**, select **Create**. +4. Enter the following information: - **ACL name**: Provide a descriptive name. - **IP range**: Enter a range of IPv4 or IPv6 addresses (limited to a maximum of /24 for IPv4 and /64 for IPv6). -6. Click **Create**. +5. Select **Create**. diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.mdx index 56962eb990b86a0..bf043e32f70908b 100644 --- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.mdx +++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.mdx @@ -8,7 +8,7 @@ head: content: Set up outgoing zone transfers (Cloudflare as Primary) --- -import { Render, TabItem, Tabs, APIRequest } from "~/components"; +import { Render, TabItem, Tabs, APIRequest, DashButton } from "~/components"; With [outgoing zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-primary/), you can keep Cloudflare as your primary DNS provider and use one or more secondary providers for increased availability and fault tolerance. @@ -64,16 +64,18 @@ You only need to create a peer DNS server if you want: To create a peer using the dashboard: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account. -2. Go to **Manage Account** > **Configurations**. -3. Select **DNS Zone Transfers**. -4. For **Peer DNS servers**, select **Create**. -5. Enter the following information, paying particular attention to: +1. In the Cloudflare dashboard, go to the account **Settings** page. + + + +2. Go to **DNS Settings**. +3. Under **DNS Zone Transfers**, for **Peer DNS servers**, select **Create**. +4. Enter the following information, paying particular attention to: - **IP**: If configured, specifies where Cloudflare sends NOTIFY requests to. - **Port**: Specifies the IP Port for the NOTIFY IP. - **Enable incremental (IXFR) zone transfers**: Does not apply when you are using Cloudflare as your primary DNS provider (Cloudflare zones always accept IXFR requests). - **Link an existing TSIG**: If desired, link the TSIG you [previously created](#1-create-tsig-optional). -6. Select **Create**. +5. Select **Create**. diff --git a/src/content/docs/dns/zone-setups/zone-transfers/index.mdx b/src/content/docs/dns/zone-setups/zone-transfers/index.mdx index f70affbb5b786be..a366003b2bee95d 100644 --- a/src/content/docs/dns/zone-setups/zone-transfers/index.mdx +++ b/src/content/docs/dns/zone-setups/zone-transfers/index.mdx @@ -8,7 +8,7 @@ head: content: Zone transfers - Multi-provider DNS --- -import { Render } from "~/components"; +import { Render, DashButton } from "~/components"; To increase availability and fault tolerance, you can use one or more DNS provider(s) alongside Cloudflare in case one provider becomes unavailable (known as a [peer DNS server](#peer-dns-server)). Your providers will then transfer DNS records between themselves using authoritative ([AXFR](https://datatracker.ietf.org/doc/html/rfc5936)) or incremental ([IXFR](https://datatracker.ietf.org/doc/html/rfc1995)) zone transfers. @@ -25,7 +25,13 @@ Peer DNS servers can be used as primary and secondary external DNS servers. The -You can manage peers via the [API](/api/resources/dns/subresources/zone_transfers/subresources/peers/methods/list/) or the dashboard by going to **Manage Account** > **Configurations** > **DNS Zone Transfers**. +You can manage peers via the [API](/api/resources/dns/subresources/zone_transfers/subresources/peers/methods/list/) or the dashboard: + +1. In the Cloudflare dashboard, go to the account **Settings** page. + + + +2. Refer to **DNS Settings** > **DNS Zone Transfers**. Depending on the usage of the peer, the fields are interpreted in a different way: From 3b8f030553a80452e9d0988d606431039bad278e Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Thu, 4 Sep 2025 09:16:08 +0100 Subject: [PATCH 2/3] Update onboard domain instructions in cf-as-secondary/setup --- .../zone-transfers/cloudflare-as-secondary/setup.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup.mdx index 257c8f6d3742523..58cc9d9053c6900 100644 --- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup.mdx +++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup.mdx @@ -72,9 +72,9 @@ Get the following values from your Cloudflare account: To create a secondary zone using the dashboard: 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account. -2. In the top navigation bar, click **Add** > **Connect a domain**. +2. Select **Onboard a domain**. 3. Enter your zone name and choose **Secondary DNS** (if this option is not available, contact your account team). -4. Click **Continue**. +4. Select **Continue**. 5. Select your plan type. 6. Choose a value for **Zone refresh**, which controls the number of seconds between zone updates from your primary DNS server. :::caution @@ -84,12 +84,12 @@ To create a secondary zone using the dashboard: :::note ::: -8. Click **Continue**. -9. Review the list of transferred records and click **Continue**. +8. Select **Continue**. +9. Review the list of transferred records and select **Continue**. :::note If no records appear, you may have misconfigured the TSIG or the IP address of the peer server or the [Access Control List](/dns/zone-setups/zone-transfers/access-control-lists/cloudflare-ip-addresses/#cloudflare-as-secondary) was improperly configured at your primary DNS provider. ::: -10. Click **Initiate zone transfer**. +10. Select **Initiate zone transfer**. @@ -101,7 +101,7 @@ To create a secondary zone using the API, send a [POST](/api/resources/dns/subre At your registrar, add the secondary nameservers [specified in the Cloudflare dashboard](/dns/zone-setups/full-setup/setup/#get-nameserver-names). Do not remove your primary DNS provider's nameservers. -When you have added the Cloudflare nameservers, go into your new secondary zone and click **Done, check nameservers**. +When you have added the Cloudflare nameservers, go into your new secondary zone and select **Done, check nameservers**. ## 5. Create notifications (optional) From fd4bc73f1e674bf8805a3de60d1bd49d3f635d5b Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Thu, 4 Sep 2025 09:41:21 +0100 Subject: [PATCH 3/3] Address solo occurrence (account members) in SSL docs --- .../ssl/origin-configuration/origin-ca/troubleshooting.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx b/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx index 3e9b886bdf7821f..84f037385a4bdcf 100644 --- a/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx +++ b/src/content/docs/ssl/origin-configuration/origin-ca/troubleshooting.mdx @@ -7,7 +7,7 @@ sidebar: label: Troubleshooting --- -import { GlossaryTooltip, Render } from "~/components"; +import { GlossaryTooltip, Render, DashButton } from "~/components"; Consider the following common issues and troubleshooting steps when using [Cloudflare origin CA](/ssl/origin-configuration/origin-ca/). @@ -60,7 +60,9 @@ If the user does not have **API Access**, this error is returned. ### Solution -Make sure that the user creating the certificate has access to the API. You can check under **Account Home** > **Manage Account** > **Members**: +Make sure that the user creating the certificate has access to the API. You can check in the account **Members** page. + + - The default setting for the account is specified in the card **Enable API Access**. - Specific user API Access (which can override the default setting) is presented after selecting the user in the list of members.