diff --git a/src/content/docs/dns/additional-options/analytics.mdx b/src/content/docs/dns/additional-options/analytics.mdx index bc7f6745dd1b30..3da772f8041448 100644 --- a/src/content/docs/dns/additional-options/analytics.mdx +++ b/src/content/docs/dns/additional-options/analytics.mdx @@ -6,7 +6,7 @@ sidebar: --- -import { FeatureTable, Details } from "~/components" +import { FeatureTable, Details, DashButton } from "~/components" When you use Cloudflare DNS, you can access data about DNS queries through a variety of sources. @@ -28,8 +28,7 @@ When using GraphQL, you also have the option to get data for DNS queries across For a quick summary, view your DNS analytics on the dashboard: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain. -2. Go to **DNS** > **Analytics**. + The DNS analytics dashboard contains [four main panels](#dns-analytics-panels). The filters and time frame that you specify at the top of the page apply to all of them. 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 03f7f712f2cac4..d9a2dffb12ed0f 100644 --- a/src/content/docs/dns/additional-options/dns-zone-defaults.mdx +++ b/src/content/docs/dns/additional-options/dns-zone-defaults.mdx @@ -11,7 +11,7 @@ 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 -DNS zone defaults are only applied at the moment a new zone is created and will not impact already existing zones. Any of the values specified as default can later be adjusted within each zone, on the respective [**DNS** > **Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) or [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page. +DNS zone defaults are only applied at the moment a new zone is created and will not impact already existing zones. Any of the values specified as default can later be adjusted within each zone, on the respective [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) or [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page. ::: ## Steps diff --git a/src/content/docs/dns/additional-options/reverse-zones.mdx b/src/content/docs/dns/additional-options/reverse-zones.mdx index b7e02b27f2be0a..7d55d879daa6b4 100644 --- a/src/content/docs/dns/additional-options/reverse-zones.mdx +++ b/src/content/docs/dns/additional-options/reverse-zones.mdx @@ -5,7 +5,7 @@ sidebar: order: 5 --- -import { Details, Example } from "~/components" +import { Details, Example, DashButton } from "~/components" If you control your own IP prefix(es), you can set up reverse zones with PTR records to allow reverse DNS lookups. @@ -71,7 +71,9 @@ To set up a reverse zone, you need to create a reverse DNS zone and add PTR reco ### 2. Add PTR records -1. Go to **DNS** > **Records**. +1. In the Cloudflare dashboard, go to the **DNS Records** page. + + 2. For each IP within the prefix, add a PTR record using the least significant octet(s) as the subdomain. diff --git a/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx b/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx index e4106bdeeb361d..e8184bf187ca39 100644 --- a/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx +++ b/src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx @@ -8,7 +8,7 @@ head: content: Set up CNAME flattening --- -import { Render, TabItem, Tabs, GlossaryTooltip } from "~/components"; +import { Render, TabItem, Tabs, GlossaryTooltip, DashButton } from "~/components"; :::note @@ -26,9 +26,11 @@ For zones on paid plans, you can choose to flatten all CNAME records. This optio -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain. -2. Go to **DNS** > **Settings**. -3. Turn on the option **CNAME flattening for all CNAME records**. +1. In the Cloudflare dashboard, go to the **DNS Settings** page. + + + +2. Turn on the option **CNAME flattening for all CNAME records**. @@ -49,11 +51,10 @@ If you use this option, a special [tag](/dns/manage-dns-records/reference/record -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain. -2. In **DNS** > **Settings**, make sure that **CNAME flattening for all CNAME records** is turned off. -3. Go to **DNS** > **Records** and find the CNAME record you would like to flatten. -4. Select **Edit** and turn on the **Flatten** option. -5. Select **Save** to confirm. +1. On the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, make sure that **CNAME flattening for all CNAME records** is turned off. +2. Go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and find the CNAME record you would like to flatten. +3. Select **Edit** and turn on the **Flatten** option. +4. Select **Save** to confirm. :::note[Unavailable flatten option] For the following cases, **Flatten** will not be available: diff --git a/src/content/docs/dns/dnssec/dnssec-active-migration.mdx b/src/content/docs/dns/dnssec/dnssec-active-migration.mdx index 4ae75d5e81d76a..6096309fd1c2a4 100644 --- a/src/content/docs/dns/dnssec/dnssec-active-migration.mdx +++ b/src/content/docs/dns/dnssec/dnssec-active-migration.mdx @@ -36,7 +36,7 @@ The provider you are migrating from must allow you to add DNSKEY records on the To import the zone file using the API, refer to the [Import DNS Records endpoint](/api/resources/dns/subresources/records/methods/import/). -3. Go to **DNS** > **Settings**, and select **Enable DNSSEC**. Or use the following [API request](/api/resources/dns/subresources/dnssec/methods/edit/). +3. On the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, select **Enable DNSSEC**. Or use the following [API request](/api/resources/dns/subresources/dnssec/methods/edit/). -4. Go to **DNS** > **Settings**, and enable **Multi-signer DNSSEC**. Or use the following [API request](/api/resources/dns/subresources/dnssec/methods/edit/). +4. On the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, enable **Multi-signer DNSSEC**. Or use the following [API request](/api/resources/dns/subresources/dnssec/methods/edit/). 0xOg== ## 3. Set up registrar -1. Add Cloudflare DS record to your registrar. You can see your Cloudflare DS record on the [dashboard](https://dash.cloudflare.com/?to=/:account/:zone/dns) by going to **DNS** > **Settings** > **DS Record**. -2. Add Cloudflare assigned nameservers to your registrar. You can see your Cloudflare nameservers by going to **DNS** > **Records**. +1. Add Cloudflare DS record to your registrar. You can see your Cloudflare DS record on the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, under **DS Record**. +2. Add Cloudflare assigned nameservers to your registrar. You can see your Cloudflare nameservers on the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page At this point your zone is in a [multi-signer DNSSEC setup](/dns/dnssec/multi-signer-dnssec/). diff --git a/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx b/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx index 8c04b49ce2ce19..26d98d34da2687 100644 --- a/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx +++ b/src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx @@ -6,7 +6,7 @@ sidebar: label: Setup --- -import { Tabs, TabItem, APIRequest } from "~/components"; +import { Tabs, TabItem, APIRequest, DashButton } from "~/components"; This page explains how you can enable [multi-signer DNSSEC](/dns/dnssec/multi-signer-dnssec/about/) with Cloudflare, using the [model 2](/dns/dnssec/multi-signer-dnssec/about/#model-2) as described in [RFC 8901](https://www.rfc-editor.org/rfc/rfc8901.html). @@ -16,7 +16,7 @@ Note that: - This process requires that your other DNS provider(s) also support multi-signer DNSSEC. - Although you can complete a few steps via the dashboard, currently the whole process can only be completed using the API. -- Enabling **DNSSEC** and **Multi-signer DNSSEC** in [**DNS** > **Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) only replaces the first step in [1. Set up Cloudflare zone](#1-set-up-cloudflare-zone). You still have to follow the rest of this tutorial to complete the setup. +- Enabling **DNSSEC** and **Multi-signer DNSSEC** on the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page only replaces the first step in [1. Set up Cloudflare zone](#1-set-up-cloudflare-zone). You still have to follow the rest of this tutorial to complete the setup. ## 1. Set up Cloudflare zone @@ -26,16 +26,18 @@ If you use Cloudflare as a primary DNS provider, meaning that you manage your DN -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone. -2. Go to **DNS** > **Settings**. -3. Select **Enable DNSSEC** and **Confirm**. +1. In the Cloudflare dashboard, go to the **DNS Settings** page. + + + +2. Select **Enable DNSSEC** and **Confirm**. :::note For the purpose of this tutorial, you will update your registrar with the DS record later, in [Step 3](/dns/dnssec/multi-signer-dnssec/setup/#3-set-up-registrar). ::: -4. Also enable **Multi-signer DNSSEC** and **Multi-provider DNS**. -5. Go to **DNS** > **Records** and create the following records at your zone apex (meaning you should use `@` in the record **Name** field): +3. Also enable **Multi-signer DNSSEC** and **Multi-provider DNS**. +4. Go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and create the following records at your zone apex (meaning you should use `@` in the record **Name** field): - A [DNSKEY record](/dns/manage-dns-records/reference/dns-record-types/#ds-and-dnskey) with the zone signing key(s) (ZSKs) of your external provider(s). - An [NS record](/dns/manage-dns-records/reference/dns-record-types/#ns) with your external provider nameservers. @@ -108,17 +110,19 @@ If you use Cloudflare as a secondary DNS provider, do the following: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone. -2. Go to **DNS** > **Settings**. -3. For **DNSSEC with Secondary DNS** select **Live signing**. +1. In the Cloudflare dashboard, go to the **DNS Settings** page. + + + +2. For **DNSSEC with Secondary DNS** select **Live signing**. :::note For the purpose of this tutorial, you will update your registrar with the DS record later, in [Step 3](/dns/dnssec/multi-signer-dnssec/setup/#3-set-up-registrar). ::: -4. Also enable **Multi-signer DNSSEC**. -5. Add the zone signing key(s) (ZSKs) of your external provider(s) to a DNSKEY record at your primary DNS provider. This record should be transferred successfully to Cloudflare. -6. Add your external provider(s) nameservers as NS records on your zone apex at your primary DNS provider. These records should be transferred successfully to Cloudflare. +3. Also enable **Multi-signer DNSSEC**. +4. Add the zone signing key(s) (ZSKs) of your external provider(s) to a DNSKEY record at your primary DNS provider. This record should be transferred successfully to Cloudflare. +5. Add your external provider(s) nameservers as NS records on your zone apex at your primary DNS provider. These records should be transferred successfully to Cloudflare. @@ -164,6 +168,6 @@ $ dig dnskey @ +noall +answer | grep 256 ## 3. Set up registrar -1. Add DS records to your registrar, one for each provider. You can see your Cloudflare DS record on the [dashboard](https://dash.cloudflare.com/?to=/:account/:zone/dns) by going to **DNS** > **Settings** > **DS Record**. +1. Add DS records to your registrar, one for each provider. You can see your Cloudflare DS record on the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, under **DS Record**. 2. Update the nameserver settings at your registrar to include the nameservers of all providers you will be using for your multi-signer DNSSEC setup. \ No newline at end of file diff --git a/src/content/docs/dns/foundation-dns/setup.mdx b/src/content/docs/dns/foundation-dns/setup.mdx index d268725d4d3187..d04d2e48f4b93b 100644 --- a/src/content/docs/dns/foundation-dns/setup.mdx +++ b/src/content/docs/dns/foundation-dns/setup.mdx @@ -13,6 +13,7 @@ import { Render, Details, Example, + DashButton, } from "~/components"; Advanced nameservers included with [Foundation DNS](/dns/foundation-dns/) are an opt-in configuration. @@ -78,10 +79,12 @@ To enable advanced nameservers on an existing zone: 1. Opt for advanced nameservers on your zone: - 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain. - 2. Go to **DNS** > **Records**. - 3. In the **Cloudflare nameservers** card, enable **Advanced nameservers**. - 4. After you refresh the page, the card will display the values for your advanced nameservers `NS` records. + 1. In the Cloudflare dashboard, go to the **DNS Records** page. + + + + 2. In the **Cloudflare nameservers** card, enable **Advanced nameservers**. + 3. After you refresh the page, the card will display the values for your advanced nameservers `NS` records. diff --git a/src/content/docs/dns/manage-dns-records/how-to/batch-record-changes.mdx b/src/content/docs/dns/manage-dns-records/how-to/batch-record-changes.mdx index ff41eb69474980..b926284a42bc74 100644 --- a/src/content/docs/dns/manage-dns-records/how-to/batch-record-changes.mdx +++ b/src/content/docs/dns/manage-dns-records/how-to/batch-record-changes.mdx @@ -5,7 +5,7 @@ sidebar: order: 10 --- -import { GlossaryTooltip, Example, Render } from "~/components"; +import { GlossaryTooltip, Example, Render, DashButton } from "~/components"; Cloudflare allows you to apply several changes to your zone records in just one action. You can [use the dashboard](#use-the-dashboard) to delete DNS records or update their proxy status in bulk, or [use the API](#use-the-api) to perform further batched operations. @@ -34,7 +34,10 @@ The number of records that you can operate with in one action depends on your zo -1. Go to [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records). +1. In the Cloudflare dashboard, go to the **DNS Records** page. + + + 2. Select the DNS records you want to set the proxy status for. Note that only `A`, `AAAA`, and `CNAME` records can be proxied. 3. Select **Edit records**. 4. Choose the proxy status you want to apply to the selected records. @@ -62,7 +65,10 @@ Deleting DNS records can cause downtime and cannot be reverted. Make sure you on ::: -1. Go to [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records). +1. In the Cloudflare dashboard, go to the **DNS Records** page. + + + 2. Select the DNS records you want to delete. 3. Select **Delete records**. 4. In the **Delete DNS records** prompt, type in `DELETE` and select **Delete** to confirm. diff --git a/src/content/docs/dns/manage-dns-records/how-to/create-dns-records.mdx b/src/content/docs/dns/manage-dns-records/how-to/create-dns-records.mdx index ad1b029cd9918c..f28ccbbe9af308 100644 --- a/src/content/docs/dns/manage-dns-records/how-to/create-dns-records.mdx +++ b/src/content/docs/dns/manage-dns-records/how-to/create-dns-records.mdx @@ -5,7 +5,7 @@ sidebar: order: 2 --- -import { GlossaryTooltip, Render, TabItem, Tabs, Details } from "~/components"; +import { GlossaryTooltip, Render, TabItem, Tabs, Details, DashButton } from "~/components"; Consider the sections below for step-by-step instructions on managing DNS records at Cloudflare. @@ -21,15 +21,17 @@ If your domain is added to Cloudflare by a hosting partner, manage your DNS reco To create a DNS record in the dashboard: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account and domain. -2. Go to **DNS** > **Records**. -3. Select **Add record**. -4. Choose a record [**Type**](/dns/manage-dns-records/reference/dns-record-types/). -5. Complete the required fields, which vary per record. Particularly important fields (for some records) include: +1. In the Cloudflare dashboard, go to the **DNS Records** page. + + + +2. Select **Add record**. +3. Choose a record [**Type**](/dns/manage-dns-records/reference/dns-record-types/). +4. Complete the required fields, which vary per record. Particularly important fields (for some records) include: - **Proxy status**: For `A`, `AAAA`, and `CNAME` records, decide whether hostname traffic is proxied through Cloudflare. - **TTL**: Short for [_Time to Live_](/dns/manage-dns-records/reference/ttl/), this field controls how long each record is valid and — as a result — how long it takes for record updates to reach your end users. - **Comment** and **Tag**: [Record attributes](/dns/manage-dns-records/reference/record-attributes/) meant for your reference. -6. Select **Save**. +5. Select **Save**. @@ -49,11 +51,13 @@ For specific API examples, refer to [DNS record types](/dns/manage-dns-records/r To edit DNS records in the dashboard: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account and domain. -2. Go to **DNS** > **Records**. -3. On a specific record, select **Edit**. -4. Make any necessary changes. -5. Select **Save**. +1. In the Cloudflare dashboard, go to the **DNS Records** page. + + + +2. On a specific record, select **Edit**. +3. Make any necessary changes. +4. Select **Save**. @@ -71,11 +75,13 @@ To update part of a record with the API, use a [PATCH request](/api/resources/dn To delete DNS records in the dashboard: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account and domain. -2. Go to **DNS** > **Records**. -3. On a specific record, select **Edit**. -4. Select **Delete**. -5. Select **Delete** again to confirm. +1. In the Cloudflare dashboard, go to the **DNS Records** page. + + + +2. On a specific record, select **Edit**. +3. Select **Delete**. +4. Select **Delete** again to confirm. diff --git a/src/content/docs/dns/manage-dns-records/how-to/import-and-export.mdx b/src/content/docs/dns/manage-dns-records/how-to/import-and-export.mdx index c97fbeaa53e53a..b7a1a653bff563 100644 --- a/src/content/docs/dns/manage-dns-records/how-to/import-and-export.mdx +++ b/src/content/docs/dns/manage-dns-records/how-to/import-and-export.mdx @@ -5,7 +5,7 @@ sidebar: order: 9 --- -import { Render, TabItem, Tabs, APIRequest } from "~/components"; +import { Render, TabItem, Tabs, APIRequest, DashButton } from "~/components"; Use import and export to have more control over your DNS records and make processes like migrating a domain or bulk editing [record comments](/dns/manage-dns-records/reference/record-attributes/) easier. @@ -28,11 +28,13 @@ If you are using certain record types — for example, `CNAME`, `DNAME`, `MX`, ` To import a zone file using the dashboard: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain. -2. Go to **DNS** > **Records**. -3. Select **Import and Export**. -4. For **Import DNS records**, select your [formatted file](#format-your-zone-file). -5. If you do not want [applicable records](/dns/proxy-status/) proxied, unselect **Proxy imported DNS records**. +1. In the Cloudflare dashboard, go to the **DNS Records** page. + + + +2. Select **Import and Export**. +3. For **Import DNS records**, select your [formatted file](#format-your-zone-file). +4. If you do not want [applicable records](/dns/proxy-status/) proxied, unselect **Proxy imported DNS records**. @@ -58,10 +60,12 @@ You can also bulk export records from Cloudflare. To export records using the dashboard: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain. -2. Go to **DNS** > **Records**. -3. Select **Import and Export**. -4. Select **Export**. +1. In the Cloudflare dashboard, go to the **DNS Records** page. + + + +2. Select **Import and Export**. +3. Select **Export**. diff --git a/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx b/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx index fdf379c797dd4d..b81d63fd126298 100644 --- a/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx +++ b/src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx @@ -35,7 +35,7 @@ To delegate a subdomain such as *internal.example.com*, tell DNS resolvers wher 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account. 2. Select the domain that contains the subdomain to be delegated. -3. Go to **DNS** > **Records**. +3. Go to [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records). 4. Create `NS` records for the subdomain. For example: * `internal.example.com NS ns1.externalhost.com` * `internal.example.com NS ns2.externalhost.com` diff --git a/src/content/docs/dns/manage-dns-records/reference/dns-record-types.mdx b/src/content/docs/dns/manage-dns-records/reference/dns-record-types.mdx index 41b9d2a7c30e78..7ac61e1a978861 100644 --- a/src/content/docs/dns/manage-dns-records/reference/dns-record-types.mdx +++ b/src/content/docs/dns/manage-dns-records/reference/dns-record-types.mdx @@ -355,7 +355,7 @@ If you are using Cloudflare for your [authoritative DNS](/dns/zone-setups/full-s With Enterprise accounts, you also have the option to change the SOA record values that Cloudflare will use: - As a DNS zone default: Define the SOA record values that Cloudflare will use for all new zones added to your account. Refer to [Configure DNS zone defaults](/dns/additional-options/dns-zone-defaults/) for step-by-step guidance. -- For existing zones: Override the defaults or Cloudflare-generated values by going to **DNS** > **Records** > **DNS record options**. +- For existing zones: Override the defaults or Cloudflare-generated values under **DNS record options** on the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page. :::note If you are an Enterprise customer and these options are not displayed on your Cloudflare dashboard, reach out to your account team. @@ -417,7 +417,7 @@ You only need to add NS records to your DNS records table in Cloudflare when you :::note -Your assigned Cloudflare nameservers, custom nameservers, and their corresponding [nameserver TTLs](/dns/nameservers/nameserver-options/#nameserver-ttl) are controlled via dedicated sections in [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records). For details, refer to [Nameservers](/dns/nameservers/). +Your assigned Cloudflare nameservers, custom nameservers, and their corresponding [nameserver TTLs](/dns/nameservers/nameserver-options/#nameserver-ttl) are controlled via dedicated sections on the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page. For details, refer to [Nameservers](/dns/nameservers/). ::: ### DS and DNSKEY 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 fdc607537bac81..6aa003272bfa7c 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 @@ -107,11 +107,13 @@ Cloudflare will assign an IPv4 and an IPv6 address to each ACNS name, and these -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and zone. -2. Go to **DNS** > **Records**. -3. For **Custom nameservers**, select **Configure**. -4. Select **Use your account custom nameservers** and choose a nameserver set from the list. -5. Select **Save** to confirm. +1. In the Cloudflare dashboard, go to the **DNS Records** page. + + + +2. For **Custom nameservers**, select **Configure**. +3. Select **Use your account custom nameservers** and choose a nameserver set from the list. +4. Select **Save** to confirm. diff --git a/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx b/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx index 329b30b3380eae..facb6e504bca56 100644 --- a/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx +++ b/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx @@ -12,7 +12,7 @@ description: With zone-level custom nameservers, each custom nameserver name These custom nameservers can only be used within the respective zone. --- -import { TabItem, Tabs } from "~/components"; +import { TabItem, Tabs, DashButton } from "~/components"; With zone custom nameservers (ZCNS), each custom nameserver name must be a subdomain of the zone where the custom nameservers are configured. @@ -30,11 +30,13 @@ To create zone custom nameservers: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and zone. -2. Go to **DNS** > **Records**. -3. On **Custom nameservers**, select **Configure**. -4. Select **Create custom nameservers just for `your-domain.com`** and enter the subdomains used for the ZCNS names (for example, `ns1`, `ns2`, `ns3`). -5. Select **Save** to confirm. +1. In the Cloudflare dashboard, go to the **DNS Records** page. + + + +2. On **Custom nameservers**, select **Configure**. +3. Select **Create custom nameservers just for `your-domain.com`** and enter the subdomains used for the ZCNS names (for example, `ns1`, `ns2`, `ns3`). +4. Select **Save** to confirm. @@ -56,7 +58,7 @@ The next step depends on whether you are using [Cloudflare Registrar](/registrar If you are using [Cloudflare as a secondary DNS provider](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/), you can still set up zone custom nameservers. After following the [steps above](/dns/nameservers/custom-nameservers/zone-custom-nameservers/#primary-full-setup-zones) to create zone custom nameservers, do the following: -1. Get the ZCNS IPs. You can see them on the dashboard (**DNS** > **Records**) or you can use the [Zone details endpoint](/api/resources/zones/methods/get/) to get the `vanity_name_servers_ips`. +1. Get the ZCNS IPs. You can find them on the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page or you can use the [Zone details endpoint](/api/resources/zones/methods/get/) to get the `vanity_name_servers_ips`. 2. At your primary DNS provider, add [`NS` records](/dns/manage-dns-records/reference/dns-record-types/#ns) and, on the subdomains that you used as ZCNS names, add `A/AAAA` records. 3. At your registrar, add the zone custom nameservers as your authoritative nameservers and as glue (A and AAAA) records ([RFC 1912](https://www.rfc-editor.org/rfc/rfc1912.html)). @@ -66,9 +68,11 @@ To remove zone custom nameservers (and their associated, read-only DNS records): -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and zone. -2. Go to **DNS** > **Records**. -3. On **Custom nameservers**, select **Disable**. +1. In the Cloudflare dashboard, go to the **DNS Records** page. + + + +2. On **Custom nameservers**, select **Disable**. diff --git a/src/content/docs/dns/nameservers/nameserver-options.mdx b/src/content/docs/dns/nameservers/nameserver-options.mdx index 327d70e20e8ae6..e655db046a4b6f 100644 --- a/src/content/docs/dns/nameservers/nameserver-options.mdx +++ b/src/content/docs/dns/nameservers/nameserver-options.mdx @@ -54,7 +54,7 @@ If you choose this option and you also want to use DNSSEC on your zone, make sur ## Nameserver TTL -For both Cloudflare nameservers (standard or advanced) and custom nameservers, the `NS` record time-to-live (TTL) is controlled by the specific setting in **DNS** > **Records** > **DNS record options**. +For both Cloudflare nameservers (standard or advanced) and custom nameservers, the `NS` record time-to-live (TTL) is controlled by the specific setting on the **DNS Records** page, under **DNS record options**. The default TTL is 24 hours (or 86,400 seconds), but you have the option to lower this value depending on your needs. For example, shorter TTLs can be useful when you are changing nameservers or migrating a zone. Accepted values range from 30 to 86,400 seconds. diff --git a/src/content/docs/dns/reference/analytics-api-properties.mdx b/src/content/docs/dns/reference/analytics-api-properties.mdx index 49609ca177431a..5dba4ea9d16960 100644 --- a/src/content/docs/dns/reference/analytics-api-properties.mdx +++ b/src/content/docs/dns/reference/analytics-api-properties.mdx @@ -18,7 +18,7 @@ This page describes API properties that you can use in requests to the [DNS anal :::caution[Warning] The [DNS analytics API](/api/resources/dns/subresources/analytics/subresources/reports/methods/get/), along with the following [API properties](/dns/reference/analytics-api-properties/), will be deprecated soon. -To access the new analytics dashboard, go to **DNS** > **Analytics**. Refer to [Analytics and logs](/dns/additional-options/analytics/) for details. +To access the new analytics dashboard, go to [**DNS Analytics**](https://dash.cloudflare.com//?to=/:account/:zone/dns/analytics). Refer to [Analytics and logs](/dns/additional-options/analytics/) for details. ::: ## Metrics diff --git a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx index 330d149b6485cd..164151b8fbf0ed 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx @@ -8,7 +8,7 @@ description: >- If you initially configured a full setup you can later convert your zone to use incoming zone transfers (Cloudflare as secondary). --- -import { Tabs, TabItem, Render, GlossaryTooltip } from "~/components"; +import { Tabs, TabItem, Render, GlossaryTooltip, DashButton } from "~/components"; If you initially configured a [full setup](/dns/zone-setups/full-setup/), you can later convert your zone to use [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/). @@ -50,9 +50,13 @@ Follow the steps below to achieve this conversion. ## 3. Convert the zone and initiate zone transfers 1. Use the [Edit Zone endpoint](/api/resources/zones/methods/edit/) with `type` set to `secondary` to convert the zone type. The existing records will remain in place. -2. Go to **DNS** > **Settings** > **DNS Zone Transfers** and select **Manage linked peers**. +2. In the Cloudflare dashboard, go to the **DNS Settings** page. + + + +3. Select **Manage linked peers** under **DNS Zone Transfers**. 3. Link the peer server you created in the previous steps and select **Save**. -4. On **DNS** > **Settings**, select **Initiate zone transfer**. +4. Back to the the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, select **Initiate zone transfer**. 5. Confirm the DNS records are transferring as expected. -6. Go to [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) and take note of your new **Cloudflare Nameservers**. +6. Go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and take note of your new **Cloudflare Nameservers**. 7. At your domain registrar (or parent zone), [update your nameservers](/dns/nameservers/update-nameservers/) to include the `secondary.cloudflare.com` nameservers. diff --git a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx index 3cfc45799fcab8..9f4272d9d22dcc 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx @@ -8,7 +8,7 @@ description: >- If you initially set up a partial domain on Cloudflare, you can later migrate it to a full setup. --- -import { Render } from "~/components"; +import { Render, DashButton } from "~/components"; If you initially set up a partial domain on Cloudflare, you can later migrate it to a [full setup](/dns/zone-setups/full-setup/). @@ -37,7 +37,7 @@ At least 24 hours prior to converting your zone, disable DNSSEC at your authorit :::note -As a best practice, you should also delete the previous [zone activation TXT record](/dns/zone-setups/partial-setup/setup/#1-convert-your-zone-and-review-dns-records) at your authoritative DNS provider. To locate this value in the Cloudflare dashboard, go to **DNS** > **Records** and find the **Verification TXT Record**. +As a best practice, you should also delete the previous [zone activation TXT record](/dns/zone-setups/partial-setup/setup/#1-convert-your-zone-and-review-dns-records) at your authoritative DNS provider. To locate this value in the Cloudflare dashboard, go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and find the **Verification TXT Record**. ::: @@ -45,13 +45,16 @@ As a best practice, you should also delete the previous [zone activation TXT rec In the Cloudflare dashboard: -1. Go to **DNS** > **Settings**. +1. In the Cloudflare dashboard, select your partial zone and go to the **DNS Settings** page. + + + 2. Select **Convert to Primary DNS** (this will not affect how your traffic is proxied). 3. Import your records into Cloudflare DNS and verify that they have been configured correctly. Usually, you will want to import [unproxied records](/dns/proxy-status/). ## 4. Activate full setup -Get your assigned Cloudflare nameservers from **DNS** > **Records** and [update your nameservers](/dns/nameservers/update-nameservers/) at your registrar. +Get your assigned Cloudflare nameservers from the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and [update your nameservers](/dns/nameservers/update-nameservers/) at your registrar. :::caution @@ -59,7 +62,8 @@ If you are counting on Universal SSL certificates to cover your website or appli ::: -Cloudflare recommends that you also [enable DNSSEC](/dns/dnssec/) from **DNS** > **Settings** and add the DS record to your registrar. +Cloudflare recommends that you also [enable DNSSEC](/dns/dnssec/) from the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page + and add the DS record to your registrar. Once all the DNS TTLs expire, all your DNS queries will be answered by the Cloudflare global network. diff --git a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-secondary.mdx b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-secondary.mdx index 97b983cc7daaf0..9e32774f326d37 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-secondary.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-secondary.mdx @@ -8,7 +8,7 @@ description: >- If you initially set up a partial zone on Cloudflare, you can later convert it to use a secondary setup. --- -import { Details, Render, TabItem, Tabs } from "~/components"; +import { Details, Render, TabItem, Tabs, DashButton } from "~/components"; If you initially set up a [partial zone](/dns/zone-setups/partial-setup/) on Cloudflare, you can later convert it to use a [secondary setup](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/). @@ -98,7 +98,7 @@ This step is essential so that Cloudflare can keep the proxy status of the recor 3. Use the [Edit Zone endpoint](/api/resources/zones/methods/edit/) with `type` set to `secondary`, to convert the zone type. - You can verify if it answers as expected by querying the new assigned secondary nameservers. You can find your nameservers in [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records), and they should follow a format like `ns0123.secondary.cloudflare.com`. + You can verify if it answers as expected by querying the new assigned secondary nameservers. You can find your nameservers on the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page, and they should follow a format like `ns0123.secondary.cloudflare.com`. ```bash # Replace ns0123 with your actual Cloudflare nameservers @@ -126,7 +126,10 @@ If you keep any DNS records that still refer `cdn.cloudflare.net`, HTTP traffic -1. Go to **DNS** > **Records**. +1. In the Cloudflare dashboard, go to the **DNS Settings** page. + + + 2. Under **DNS Zone Transfers**, select **Manage linked peers**. 3. Choose a value for **Zone refresh**, which controls the number of seconds between zone updates from your primary DNS server. :::caution @@ -141,4 +144,4 @@ Use the [Update Secondary Zone Configuration endpoint](/api/resources/dns/subres -4. In [**DNS** > **Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings), confirm the linked peer is listed under **DNS Zone Transfers**, and select **Initiate zone transfer**. Alternatively, you can use the [Force AXFR endpoint](/api/resources/dns/subresources/zone_transfers/subresources/force_axfr/methods/create/). +4. On the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, confirm the linked peer is listed under **DNS Zone Transfers**, and select **Initiate zone transfer**. Alternatively, you can use the [Force AXFR endpoint](/api/resources/dns/subresources/zone_transfers/subresources/force_axfr/methods/create/). diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx index 6fe4a10b36e94f..6c738fa967504e 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx @@ -32,7 +32,7 @@ Follow the steps below to achieve this conversion. ## 3. Convert your zone 1. Use the [Edit Zone endpoint](/api/resources/zones/methods/edit/) with `type` set to `full` to convert the zone type. Existing DNS records will not be affected. -2. Go to [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) and take note of your new **Cloudflare Nameservers**. +2. Go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and take note of your new **Cloudflare Nameservers**. 3. At your domain registrar (or parent zone), [update your nameservers](/dns/nameservers/update-nameservers/). Replace the nameservers ending in `secondary.cloudflare.com` by the ones ending in `ns.cloudflare.com`. :::note diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx index 791f12e8964d9e..209c54dd5f53f4 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx @@ -41,7 +41,7 @@ Follow the steps below to achieve this conversion. 1. Back at your Cloudflare zone, confirm that you have all the `A`, `AAAA`, or `CNAME` [DNS records](/dns/manage-dns-records/how-to/create-dns-records/) needed for the hostnames you pointed to `{your-hostname}.cdn.cloudflare.net` in the previous step. You can also delete any DNS records that have a different type, as they will no longer resolve once you convert your zone to a partial setup. 2. Use the [Edit Zone endpoint](/api/resources/zones/methods/edit/) with `type` set to `partial` to convert the zone type. Existing DNS records will not be affected. -3. On [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records), get the **Verification TXT Record** and add it at your authoritative DNS provider. +3. On the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page, get the **Verification TXT Record** and add it at your authoritative DNS provider.
diff --git a/src/content/docs/dns/zone-setups/full-setup/setup.mdx b/src/content/docs/dns/zone-setups/full-setup/setup.mdx index 57f65d23d6c928..420eb3220b0e65 100644 --- a/src/content/docs/dns/zone-setups/full-setup/setup.mdx +++ b/src/content/docs/dns/zone-setups/full-setup/setup.mdx @@ -10,7 +10,7 @@ description: >- If you want to use Cloudflare as your primary DNS provider and manage your DNS records, your domain should be using a full setup. --- -import { Render } from "~/components"; +import { Render, DashButton } from "~/components"; @@ -64,8 +64,11 @@ When you start using Cloudflare's nameservers for authoritative DNS and your zon ### Get nameserver names -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain. -2. On **Overview**, locate the nameserver names in **2. Replace with Cloudflare's nameservers**. +1. In the Cloudflare dashboard, go to the zone **Overview** page. + + + +2. Locate the nameserver names in **2. Replace with Cloudflare's nameservers**. ![Find nameserver names on the Overview page of your domain](~/assets/images/dns/nameserver-names.png) diff --git a/src/content/docs/dns/zone-setups/partial-setup/setup.mdx b/src/content/docs/dns/zone-setups/partial-setup/setup.mdx index 6e72601c0b6620..fdb19a5eae59b3 100644 --- a/src/content/docs/dns/zone-setups/partial-setup/setup.mdx +++ b/src/content/docs/dns/zone-setups/partial-setup/setup.mdx @@ -42,7 +42,7 @@ Partial setups are not supported on Cloudflare Registrar domains. 1. On the **Overview** page, select **Convert to CNAME DNS Setup**. 2. Select **Convert** to confirm. -3. Save the information from the **Verification TXT Record**. If you lose the information, you can also access it by going to **DNS** > **Records** > **Verification TXT Record**. +3. Save the information from the **Verification TXT Record**. If you lose the information, you can also access it on the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page, under **Verification TXT Record**. 4. Make sure that you have all the DNS records (A, AAAA, or CNAME) for subdomains that you want to proxy through Cloudflare. diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/dnssec.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/dnssec.mdx index 8382a4194ef434..7d87536cf5ebfd 100644 --- a/src/content/docs/dns/zone-setups/subdomain-setup/dnssec.mdx +++ b/src/content/docs/dns/zone-setups/subdomain-setup/dnssec.mdx @@ -24,7 +24,7 @@ Ideally, you should also wait 12 to 24 hours after enabling DNSSEC on the parent 3. [Enable DNSSEC](/dns/dnssec/) for the child zone and save the information provided within the DS record output. -4. In the **DNS** > **Records** settings of the parent zone, [add the DS record](/dns/manage-dns-records/how-to/create-dns-records/) from the previous step. +4. On the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page of the parent zone, [add the DS record](/dns/manage-dns-records/how-to/create-dns-records/) from the previous step. ![Screenshot showing how to add a DS record within Cloudflare](~/assets/images/dns/ds-record-example.png) diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx index e6ef6e8ae884eb..f594b4af2867e1 100644 --- a/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx +++ b/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx @@ -25,7 +25,7 @@ This process may incur in downtime, as it is not possible to add address records 1. (Optional) In the parent zone, migrate over any settings - [WAF custom rules](/waf/custom-rules/), [Rules](/rules/), [Workers](/workers/), and more - that might be needed for the child domain. 2. (Optional) If necessary, [order an advanced SSL certificate](/ssl/edge-certificates/advanced-certificate-manager/) that covers the child domain and any deeper subdomains. -3. In the parent zone, go to **DNS** > **Records**. +3. In the parent zone, go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page. 4. Delete one of the `NS` records defined for the child domain. 5. Edit the remaining `NS` record to create the subdomain address record. 6. [Import](/dns/manage-dns-records/how-to/import-and-export/#import-records) the records you had obtained [before you began](#before-you-begin). diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx index 338d05934e7fa9..ae41f5d84ed606 100644 --- a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx +++ b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-full.mdx @@ -27,9 +27,9 @@ If you have not yet created DNS records covering your subdomain in the parent zo 2. Complete the configuration accordingly for [full](/dns/zone-setups/full-setup/setup/) or [secondary](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/) setup. -3. Get the nameserver names for the subdomain. These can be found within your newly created child zone in [DNS > Records](https://dash.cloudflare.com/?to=/:account/:zone/dns/records), and will **not** be the same nameservers as the ones used in the parent zone. +3. Get the nameserver names for the subdomain. These can be found within your newly created child zone on the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page, and will **not** be the same nameservers as the ones used in the parent zone. -4. Within the **DNS** > **Records** of the parent zone, [add](/dns/manage-dns-records/how-to/create-dns-records/) two `NS` records for the subdomain you want to delegate. +4. On the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page of the parent zone, [add](/dns/manage-dns-records/how-to/create-dns-records/) two `NS` records for the subdomain you want to delegate. For example, if you delegated `www.example.com`, you might add the following records to `example.com`: @@ -62,13 +62,13 @@ If you have already created DNS records covering your subdomain in the parent zo 5. In the child zone, [order an advanced SSL certificate](/ssl/edge-certificates/advanced-certificate-manager/) that covers the child subdomain and any deeper subdomains (if present). -6. Get the nameserver names for the subdomain. These can be found within your newly created child zone in [DNS > Records](https://dash.cloudflare.com/?to=/:account/:zone/dns/records), and will **not** be the same nameservers as the ones used in the parent zone. +6. Get the nameserver names for the subdomain. These can be found within your newly created child zone on the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page, and will **not** be the same nameservers as the ones used in the parent zone. :::note If the parent zone is on Cloudflare, steps 7 and 9 below can be achieved via API. Use the [Batch DNS records](/api/resources/dns/subresources/records/methods/batch/) endpoint to delete and create or update DNS records within a single request. Refer to [Batch record changes](/dns/manage-dns-records/how-to/batch-record-changes/) for further guidance. ::: -7. Within the **DNS** > **Records** of the parent zone, update existing address records (`A/AAAA`) on your subdomain to `NS` records. If you only have one address record, update the existing one and add a new `NS` record. If you have multiple address records, update any two of them. +7. On the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page of the parent zone, update existing address records (`A/AAAA`) on your subdomain to `NS` records. If you only have one address record, update the existing one and add a new `NS` record. If you have multiple address records, update any two of them. For example, to delegate the subdomain `www.example.com`, the updated records in the parent zone `example.com` should contain `NS` records similar to the following: @@ -81,7 +81,7 @@ If you have already created DNS records covering your subdomain in the parent zo 8. Flush the address records of your subdomain in public resolvers ([1.1.1.1](https://1.1.1.1/purge-cache/) and [8.8.8.8](https://developers.google.com/speed/public-dns/cache)). -9. In the **DNS** > **Records** of the parent zone, [delete](/dns/manage-dns-records/how-to/create-dns-records/#delete-dns-records) all the remaining records on the delegated subdomain, except the `NS` records that you created in step 7. +9. On the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page of the parent zone, [delete](/dns/manage-dns-records/how-to/create-dns-records/#delete-dns-records) all the remaining records on the delegated subdomain, except the `NS` records that you created in step 7. Also delete all DNS records deeper than the delegated subdomain. For example, if you are delegating `www.example.com`, records for `api.www.example.com` should only exist in the new child zone. diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx index b1737b4907bd88..1fba5db2d0441b 100644 --- a/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx +++ b/src/content/docs/dns/zone-setups/subdomain-setup/setup/parent-on-partial.mdx @@ -30,7 +30,7 @@ If you have not yet created a DNS record covering your subdomain in the parent z 2. Select either Business or Enterprise as your zone plan and complete the onboarding flow according to your needs. 3. On the [Overview page](https://dash.cloudflare.com/?to=/:account/:zone), select **Convert to CNAME DNS Setup**. 4. Confirm that you have created all the [DNS records](/dns/manage-dns-records/how-to/create-dns-records/) needed for your child zone. -5. On [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records), get the **Verification TXT Record** and add it at your authoritative DNS provider. +5. On the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page, get the **Verification TXT Record** and add it at your authoritative DNS provider.
@@ -91,7 +91,7 @@ If you have already created a DNS record covering your subdomain in the parent z 7. Within a short period of time, the child zone should be active. -8. Within the **DNS** > **Records** of the parent zone, [delete](/dns/manage-dns-records/how-to/create-dns-records/#delete-dns-records) any `A`, `AAAA`, or `CNAME` records referencing the subdomain or any of its deeper subdomains. +8. On the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page of the parent zone, [delete](/dns/manage-dns-records/how-to/create-dns-records/#delete-dns-records) any `A`, `AAAA`, or `CNAME` records referencing the subdomain or any of its deeper subdomains. @@ -111,7 +111,7 @@ If you have already created a DNS record covering your subdomain in the parent z 6. In the child zone, [order an advanced SSL certificate](/ssl/edge-certificates/advanced-certificate-manager/) that covers the child subdomain and any deeper subdomains. -7. On [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records), get the **Verification TXT Record** and add it at your authoritative DNS provider. +7. On the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page, get the **Verification TXT Record** and add it at your authoritative DNS provider.
@@ -132,7 +132,7 @@ After creating the record, you can use this [Dig Web Interface link](https://dig That record must remain in place for as long as your subdomain is active on the partial setup on Cloudflare. 8. Within a short period of time, the child zone should be active. -9. Within the **DNS** > **Records** of the parent zone, [delete](/dns/manage-dns-records/how-to/create-dns-records/#delete-dns-records) any previous `A`, `AAAA`, or `CNAME` records referencing the subdomain or any of its deeper subdomains. +9. On the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page of the parent zone, [delete](/dns/manage-dns-records/how-to/create-dns-records/#delete-dns-records) any previous `A`, `AAAA`, or `CNAME` records referencing the subdomain or any of its deeper subdomains. 10. At your authoritative DNS provider, confirm you have `CNAME` records pointing to `{your-hostname}.cdn.cloudflare.net` for the subdomain you have added and any deeper subdomain records you want to proxy through Cloudflare. diff --git a/src/content/docs/dns/zone-setups/troubleshooting/domain-deleted.mdx b/src/content/docs/dns/zone-setups/troubleshooting/domain-deleted.mdx index b7cb40b21568e3..ea8b35b1ecb50c 100644 --- a/src/content/docs/dns/zone-setups/troubleshooting/domain-deleted.mdx +++ b/src/content/docs/dns/zone-setups/troubleshooting/domain-deleted.mdx @@ -34,7 +34,7 @@ If your domain was using a [full setup](/dns/zone-setups/full-setup/), your regi - Ensure Cloudflare’s nameservers are the only two nameservers listed in the domain registration details. - Ensure nameservers are spelled correctly in the domain registration. -2. Confirm that the nameservers exactly match the nameservers provided within the **Cloudflare Nameservers** card in **DNS** > **Records**. +2. Confirm that the nameservers exactly match the nameservers provided within the **Cloudflare Nameservers** card on the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page. 3. If you identify incorrect information, log in to your domain provider’s portal to make updates or contact your domain provider for assistance. diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/dnssec-for-primary.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/dnssec-for-primary.mdx index 6ddd6ccc80a074..8acbee4b2b839e 100644 --- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/dnssec-for-primary.mdx +++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/dnssec-for-primary.mdx @@ -23,7 +23,7 @@ Note that: - This process requires that your other DNS provider(s) also support multi-signer DNSSEC. - Although you can complete a few steps via the dashboard, currently the whole process can only be completed using the API. -- Enabling **DNSSEC** and **Multi-signer DNSSEC** in [**DNS** > **Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) only replaces the first step below. You still have to follow the rest of this tutorial to complete the setup. +- Enabling **DNSSEC** and **Multi-signer DNSSEC** in [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) only replaces the first step below. You still have to follow the rest of this tutorial to complete the setup. ## Steps @@ -80,6 +80,6 @@ $ dig dnskey @ +noall +answer | grep 256 -4. Add DS records to your registrar, one for each provider. You can see your Cloudflare DS record on the [dashboard](https://dash.cloudflare.com/?to=/:account/:zone/dns) by going to **DNS** > **Settings** > **DS Record**. +4. Add DS records to your registrar, one for each provider. You can see your Cloudflare DS record on the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, under **DS Record**. The nameserver settings at your registrar should include the nameservers of all providers you will be using for your multi-signer DNSSEC setup. 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 dfbd6ae4473734..422cec31ef3fd6 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 @@ -81,12 +81,13 @@ If you previously [created a peer DNS server](#2-create-peer-dns-server-optional To link a primary zone to a peer using the dashboard: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login). -2. Select your account and zone. -3. Go to **DNS** > **Settings**. -4. For **DNS Zone Transfers**, select **Manage linked peers**. -5. Select a peer. -6. Select **Save**. +1. In the Cloudflare dashboard, go to the **DNS Settings** page. + + + +2. For **DNS Zone Transfers**, select **Manage linked peers**. +3. Select a peer. +4. Select **Save**. @@ -116,10 +117,12 @@ If your account [zone defaults](/dns/additional-options/dns-zone-defaults/) are -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login). -2. Select your account and zone. -3. Go to **DNS** > **Settings**. -4. Enable **Multi-provider DNS**. + +1. In the Cloudflare dashboard, go to the **DNS Settings** page. + + + +2. Enable **Multi-provider DNS**. @@ -145,10 +148,11 @@ When you enable outgoing zone transfers, this will send a DNS NOTIFY message to -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login). -2. Select your account and zone. -3. Go to **DNS** > **Settings**. -4. For **Outgoing Zone Transfers**, switch the toggle to **On**. +1. In the Cloudflare dashboard, go to the **DNS Settings** page. + + + +2. For **Outgoing Zone Transfers**, switch the toggle to **On**. diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary.mdx index 47d2a7e6b3011d..b9866d1b521cf9 100644 --- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary.mdx +++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary.mdx @@ -14,6 +14,7 @@ import { Tabs, GlossaryTooltip, APIRequest, + DashButton, } from "~/components"; [DNS Security Extensions (DNSSEC)](https://www.cloudflare.com/learning/dns/dns-security/) increase security by adding cryptographic signatures to DNS records. When you use multiple providers and Cloudflare is secondary, you have a few options to enable DNSSEC for records served by Cloudflare. @@ -38,13 +39,13 @@ In this setup, DNSSEC on your pirmary DNS provider does not need to be enabled. -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone. +1. In the Cloudflare dashboard, go to the **DNS Settings** page. -2. Go to **DNS** > **Settings**. + -3. Under **DNSSEC with Secondary DNS** select **Live signing**. You will then have access to several necessary values to create a **DS** record at your registrar. +2. Under **DNSSEC with Secondary DNS** select **Live signing**. You will then have access to several necessary values to create a **DS** record at your registrar. -4. +3. @@ -85,7 +86,9 @@ Pre-signed DNSSEC does not support [Secondary DNS Overrides](/dns/zone-setups/zo -1. Select your zone and go to **DNS** > **Settings**. +1. In the Cloudflare dashboard, go to the **DNS Settings** page. + + 2. Under **DNSSEC with Secondary DNS** select **Pre-signed**. @@ -103,6 +106,6 @@ Use the [Edit DNSSEC Status endpoint](/api/resources/dns/subresources/dnssec/met -3. Make sure Cloudflare nameservers are added at your registrar. You can see your Cloudflare nameservers on the dashboard by going to **DNS** > **Records**. +3. Make sure Cloudflare nameservers are added at your registrar. You can see your Cloudflare nameservers on the dashboard by going to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page. 4. Make sure there is a DS record added at your registrar. The DS record is obtained from your primary DNS provider (the signer of the zone) and is what indicates to DNS resolvers that your zone has DNSSEC enabled. diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx index 7ff1909d4d116a..cb5e18bec04f84 100644 --- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx +++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx @@ -8,7 +8,7 @@ head: content: Proxy traffic with Secondary DNS override --- -import { TabItem, Tabs, APIRequest } from "~/components"; +import { TabItem, Tabs, APIRequest, DashButton } from "~/components"; When you set up [incoming zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/) on a secondary zone, you cannot enable the proxy on any transferred DNS records by default. @@ -38,10 +38,12 @@ Before you set up Secondary DNS override, make sure that you have: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain. -2. Go to **DNS** > **Settings**. -3. Enable **Secondary DNS override**. -4. On **DNS** > **Records**, for specific A, AAAA, or CNAME records, select the grey cloud icon to set their **Proxy status** to **Proxied**. +1. In the Cloudflare dashboard, go to the **DNS Settings** page. + + + +2. Enable **Secondary DNS override**. +3. On the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page, for specific A, AAAA, or CNAME records, select the grey cloud icon to set their **Proxy status** to **Proxied**. diff --git a/src/content/partials/dns/dns-record-steps.mdx b/src/content/partials/dns/dns-record-steps.mdx index bc3b41481f4476..058a0bf5c7cacf 100644 --- a/src/content/partials/dns/dns-record-steps.mdx +++ b/src/content/partials/dns/dns-record-steps.mdx @@ -4,12 +4,15 @@ params: - example --- -import { Tabs, TabItem, Render, GlossaryTooltip } from "~/components"; +import { Tabs, TabItem, Render, GlossaryTooltip, DashButton } from "~/components"; -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and zone. -2. Go to **DNS** > **Records** and select **Add record**. +1. In the Cloudflare dashboard, go to the **DNS Records** page. + + + +2. Select **Add record**. 3. Select `A`, `AAAA`, or `CNAME` as the record **Type**, according to your needs: - To point to an IPv4 address, select `A`, use {props.name} ({props.example}) for the record **Name**, and insert the IPv4 address in the respective field. - To point to an IPv6 address, select `AAAA`, use {props.name} ({props.example}) for the record **Name**, and insert the IPv6 address in the respective field. diff --git a/src/content/partials/dns/dns-scan-intro.mdx b/src/content/partials/dns/dns-scan-intro.mdx index 0ba55288bbc8e6..5258e416a02d05 100644 --- a/src/content/partials/dns/dns-scan-intro.mdx +++ b/src/content/partials/dns/dns-scan-intro.mdx @@ -3,4 +3,4 @@ --- -Cloudflare can [automatically scan for common records](/dns/zone-setups/reference/dns-quick-scan/) and add them to the [DNS zone](/dns/concepts/#zone) for you, or you can add records manually. These records show up under your domain on the **DNS** > **Records** page of the dashboard. +Cloudflare can [automatically scan for common records](/dns/zone-setups/reference/dns-quick-scan/) and add them to the [DNS zone](/dns/concepts/#zone) for you, or you can add records manually. These records show up under your domain on the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page of the dashboard. diff --git a/src/content/partials/dns/dnssec-cloudflare-steps.mdx b/src/content/partials/dns/dnssec-cloudflare-steps.mdx index a2cf77bb5572d6..d066c3e5a606e9 100644 --- a/src/content/partials/dns/dnssec-cloudflare-steps.mdx +++ b/src/content/partials/dns/dnssec-cloudflare-steps.mdx @@ -3,7 +3,11 @@ --- -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain. -2. Go to **DNS** > **Settings**. -3. For **DNSSEC**, click **Enable DNSSEC**. -4. In the dialog, you have access to several necessary values to help you create a **DS** record at your registrar. Once you close the dialog, you can access this information by clicking **DS record** on the **DNSSEC** card. +import { DashButton } from "~/components"; + +1. In the Cloudflare dashboard, go to the **DNS Settings** page. + + + +2. For **DNSSEC**, click **Enable DNSSEC**. +3. In the dialog, you have access to several necessary values to help you create a **DS** record at your registrar. Once you close the dialog, you can access this information by clicking **DS record** on the **DNSSEC** card. diff --git a/src/content/partials/dns/secondary-conversion-unlink.mdx b/src/content/partials/dns/secondary-conversion-unlink.mdx index 2fdc6a35986302..3addd6a512c230 100644 --- a/src/content/partials/dns/secondary-conversion-unlink.mdx +++ b/src/content/partials/dns/secondary-conversion-unlink.mdx @@ -3,8 +3,13 @@ --- -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone. -2. Go to **DNS** > **Settings** > **DNS Zone Transfers** and select **Manage linked peers**. +import { DashButton } from "~/components"; + +1. In the Cloudflare dashboard, go to the **DNS Settings** page. + + + +2. Under **DNS Zone Transfers**, and select **Manage linked peers**. 3. Unlink the peer and select **Save**. At this point, your zone will be read-only. \ No newline at end of file