diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/salesforce-commerce-cloud.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/salesforce-commerce-cloud.mdx index 8db4f8b6a4b1430..10f92489fc8ee26 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/salesforce-commerce-cloud.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/salesforce-commerce-cloud.mdx @@ -32,9 +32,9 @@ To enable O2O requires the following: 1. Your SFCC environment must be configured as an "SFCC Proxy Zone". If you currently have an "SFCC Legacy Zone", you cannot enable O2O. More details on the different types of SFCC configurations can be found in the [Salesforce FAQ on SFCC Proxy Zones](https://help.salesforce.com/s/articleView?id=cc.b2c_ecdn_proxy_zone_faq.htm&type=5). 2. Your own Cloudflare zone on an Enterprise plan. -If you meet the above requirements, O2O can then be enabled per hostname. To enable O2O for a specific hostname within your Cloudflare zone, [create](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) a Proxied `CNAME` DNS record with a target of the `CNAME` provided by SFCC Business Manager, which is the dashboard used by SFCC customers to configure their storefront environment. +If you meet the above requirements, O2O can then be enabled per hostname. To enable O2O for a specific hostname within your Cloudflare zone, [create](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) a Proxied CNAME DNS record with a target of the CNAME provided by SFCC Business Manager, which is the dashboard used by SFCC customers to configure their storefront environment. -The `CNAME` provided by SFCC Business Manager will resemble `commcloud.prod-abcd-example-com.cc-ecdn.net` and contains 3 distinct parts. For each hostname routing traffic to SFCC, be sure to update each part of the example `CNAME` to match your SFCC environment: +The CNAME provided by SFCC Business Manager will resemble `commcloud.prod-abcd-example-com.cc-ecdn.net` and contains 3 distinct parts. For each hostname routing traffic to SFCC, be sure to update each part of the example CNAME to match your SFCC environment: 1. **Environment**: `prod` should be changed to `prod` or `dev` or `stg`. 2. **Realm**: `abcd` should be changed to the Realm ID assigned to you by SFCC. diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx index ffaf1ccff100531..dda50fdb9ed58ba 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting.mdx @@ -19,24 +19,24 @@ If a domain is flagged by the CA, you need to contact Support before validation ## Certificate Authority Authorization (CAA) records -`CAA` is a DNS resource record type defined in [RFC 6844](https://datatracker.ietf.org/doc/html/rfc6844) that allows a domain owner to indicate which CAs are allowed to issue certificates for them. +CAA is a DNS resource record type defined in [RFC 6844](https://datatracker.ietf.org/doc/html/rfc6844) that allows a domain owner to indicate which CAs are allowed to issue certificates for them. ### For SaaS providers -If your customer has `CAA` records set on their domain, they will either need to add the following or remove `CAA` entirely: +If your customer has CAA records set on their domain, they will either need to add the following or remove CAA entirely: ```txt example.com. IN CAA 0 issue "letsencrypt.org" example.com. IN CAA 0 issue "pki.goog" ``` -While it is possible for `CAA` records to be set on the subdomain your customer wishes to use with your service, it will usually be set on the domain apex. If they have `CAA` records on the subdomain, those will also have to be removed. +While it is possible for CAA records to be set on the subdomain your customer wishes to use with your service, it will usually be set on the domain apex. If they have CAA records on the subdomain, those will also have to be removed. ### For SaaS customers -In some cases, the validation may be prevented because your hostname points to a `CNAME` target where `CAA` records are defined. +In some cases, the validation may be prevented because your hostname points to a CNAME target where CAA records are defined. -In this case you would need to either select a Certificate Authority whose `CAA` records are present at the target, or review the configuration with the service provider that owns the target. +In this case you would need to either select a Certificate Authority whose CAA records are present at the target, or review the configuration with the service provider that owns the target. *** diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/setup.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/setup.mdx index b23dc4fb2bd28a7..c96a3d710db5496 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/setup.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/setup.mdx @@ -49,35 +49,35 @@ These IP addresses are different than those associated with your Cloudflare zone ### 3. Have customer create DNS record -To finish the custom hostname setup, your customer can set up either an `A` or `CNAME` record at their authoritative DNS provider. +To finish the custom hostname setup, your customer can set up either an A or CNAME record at their authoritative DNS provider. :::note -If you want your customers to be able to use `CNAME` records, you will need to complete the [normal setup process](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/) as well. +If you want your customers to be able to use CNAME records, you will need to complete the [normal setup process](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/) as well. ::: -#### `A` record +#### A record -If your customer uses an `A` record at their authoritative DNS provider, they need to point their hostname to the IP prefixed allocated for your account. +If your customer uses an A record at their authoritative DNS provider, they need to point their hostname to the IP prefixed allocated for your account. -Your customer's `A` record might look like the following: +Your customer's A record might look like the following: ```txt example.com. 60 IN A 192.0.2.1 ``` -#### `CNAME` record +#### CNAME record -If your customer uses a `CNAME` record at their authoritative DNS, they need to point their hostname to your [`CNAME` target](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/#2-optional-create-cname-target) [^1]. +If your customer uses a CNAME record at their authoritative DNS, they need to point their hostname to your [CNAME target](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/#2-optional-create-cname-target) [^1]. -Your customer's `CNAME` record might look like the following: +Your customer's CNAME record might look like the following: ```txt mystore.com CNAME customers.saasprovider.com diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started.mdx index 149e050ea2c3c80..6fae860657efcd7 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started.mdx @@ -26,9 +26,9 @@ import { Example, Render } from "~/components" ### 2. (Optional) Create CNAME target -The `CNAME` target — optional, but highly encouraged — provides a friendly and more flexible place for customers to [route their traffic](#3-have-customer-create-cname-record). You may want to use a subdomain such as `customers..com`. +The CNAME target — optional, but highly encouraged — provides a friendly and more flexible place for customers to [route their traffic](#3-have-customer-create-cname-record). You may want to use a subdomain such as `customers..com`. -[Create](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) a proxied `CNAME` that points your `CNAME` target to your fallback origin (can be a wildcard such as `*.customers.saasprovider.com`). +[Create](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) a proxied CNAME that points your CNAME target to your fallback origin (can be a wildcard such as `*.customers.saasprovider.com`). @@ -46,11 +46,11 @@ The `CNAME` target — optional, but highly encouraged — provides a friendly a ### 3. Have customer create CNAME record -To finish the custom hostname setup, your customer needs to set up a `CNAME` record at their authoritative DNS that points to your [`CNAME` target](#2-optional-create-cname-target) [^1]. +To finish the custom hostname setup, your customer needs to set up a CNAME record at their authoritative DNS that points to your [CNAME target](#2-optional-create-cname-target) [^1]. -Your customer's `CNAME` record might look like the following: +Your customer's CNAME record might look like the following: ```txt mystore.example.com CNAME customers.saasprovider.com @@ -67,7 +67,7 @@ B --> C[proxy-fallback.saasprovider.com]
-Requests to `mystore.example.com` would go to your `CNAME` target (`customers.saasprovider.com`), which would then route to your fallback origin (`proxy-fallback.saasprovider.com`). +Requests to `mystore.example.com` would go to your CNAME target (`customers.saasprovider.com`), which would then route to your fallback origin (`proxy-fallback.saasprovider.com`). [^1]: diff --git a/src/content/docs/dns/cname-flattening/cname-flattening-diagram.mdx b/src/content/docs/dns/cname-flattening/cname-flattening-diagram.mdx index 13bc8d0fe069b47..0f793ad00ec1631 100644 --- a/src/content/docs/dns/cname-flattening/cname-flattening-diagram.mdx +++ b/src/content/docs/dns/cname-flattening/cname-flattening-diagram.mdx @@ -12,20 +12,20 @@ description: Consider an example use case and the main steps involved in CNAME f import { Example } from "~/components" -With `CNAME` flattening, Cloudflare returns an IP address instead of the target hostname that a `CNAME` record points to. +With CNAME flattening, Cloudflare returns an IP address instead of the target hostname that a CNAME record points to. This process supports a few features and delivers better performance and flexibility, as mentioned in the [CNAME flattening concept page](/dns/cname-flattening/). -Consider the diagram below to have an overview of the steps that may be involved in `CNAME` flattening. +Consider the diagram below to have an overview of the steps that may be involved in CNAME flattening. :::note -Note that this is a simpler scenario. Cases where `CNAME` flattening is optional and/or the target hostname is not external to Cloudflare work differently. +Note that this is a simpler scenario. Cases where CNAME flattening is optional and/or the target hostname is not external to Cloudflare work differently. ::: ## Example use case -* `domain.test` is a zone on Cloudflare and has the following `CNAME` record: +* `domain.test` is a zone on Cloudflare and has the following CNAME record: @@ -83,5 +83,5 @@ accDescr: Diagram of CNAME flattening process when there is a request for a doma ## Aspects to consider -* If the `CNAME` record is proxied in Cloudflare, the answer is made up of multiple [Cloudflare IPs](https://www.cloudflare.com/ips/) and its Time to Live (TTL) is set to `300`. -* If the `CNAME` record in Cloudflare is not proxied, the flattened answer consists of the IP address from the external DNS provider and its TTL corresponds to the lower value between the external record and the Cloudflare `CNAME` record. +* If the CNAME record is proxied in Cloudflare, the answer is made up of multiple [Cloudflare IPs](https://www.cloudflare.com/ips/) and its Time to Live (TTL) is set to `300`. +* If the CNAME record in Cloudflare is not proxied, the flattened answer consists of the IP address from the external DNS provider and its TTL corresponds to the lower value between the external record and the Cloudflare CNAME record. diff --git a/src/content/docs/dns/cname-flattening/index.mdx b/src/content/docs/dns/cname-flattening/index.mdx index 6dcc0175ee47c39..279123e2a01359e 100644 --- a/src/content/docs/dns/cname-flattening/index.mdx +++ b/src/content/docs/dns/cname-flattening/index.mdx @@ -8,7 +8,7 @@ sidebar: import { Render } from "~/components" -`CNAME` flattening speeds up `CNAME` resolution and allows you to use a `CNAME` record at your root/apex domain (`example.com`). +CNAME flattening speeds up CNAME resolution and allows you to use a CNAME record at your root/apex domain (`example.com`). :::note @@ -20,11 +20,11 @@ This functionality is also what allows you to use a [root custom domain](/pages/ ## How it works -With `CNAME` flattening, Cloudflare finds the IP address that a `CNAME` points to. This process could involve a single lookup or multiple (if your `CNAME` points to another `CNAME`). Cloudflare then returns the final IP address instead of a `CNAME` record, helping DNS queries resolve up to 30% faster. +With CNAME flattening, Cloudflare finds the IP address that a CNAME points to. This process could involve a single lookup or multiple (if your CNAME points to another CNAME). Cloudflare then returns the final IP address instead of a CNAME record, helping DNS queries resolve up to 30% faster. -For more details on the steps involved in `CNAME` flattening, review the [CNAME flattening diagram](/dns/cname-flattening/cname-flattening-diagram/) and refer to the [Cloudflare blog post](https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/). +For more details on the steps involved in CNAME flattening, review the [CNAME flattening diagram](/dns/cname-flattening/cname-flattening-diagram/) and refer to the [Cloudflare blog post](https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/). ## Aspects to keep in mind -* `CNAME` flattening happens by default in some cases. Refer to [Setup](/dns/cname-flattening/set-up-cname-flattening/) for details. +* CNAME flattening happens by default in some cases. Refer to [Setup](/dns/cname-flattening/set-up-cname-flattening/) for details. * 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 41889d451969b0d..91e839c1b98dd37 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 @@ -14,18 +14,18 @@ import { Render, TabItem, Tabs, GlossaryTooltip } from "~/components" :::note -If the `CNAME` target is on the same zone as the `CNAME` record, Cloudflare proceeds with `CNAME` flattening and ignores the **CNAME Flattening** setting. +If the CNAME target is on the same zone as the CNAME record, Cloudflare proceeds with CNAME flattening and ignores the **CNAME Flattening** setting. ::: ## For your zone apex -`CNAME` flattening occurs by default for all plans when your domain uses a `CNAME` record for its zone apex (`example.com`, meaning the record **Name** is set to `@`). +CNAME flattening occurs by default for all plans when your domain uses a CNAME record for its zone apex (`example.com`, meaning the record **Name** is set to `@`). ## For all CNAME records -For zones on paid plans, you can choose to flatten all `CNAME` records. This option is useful for DNS-only (unproxied) `CNAME` records. [Proxied records](/dns/manage-dns-records/reference/proxied-dns-records/#proxied-records) are flattened by default as they return Cloudflare anycast IPs. +For zones on paid plans, you can choose to flatten all CNAME records. This option is useful for DNS-only (unproxied) CNAME records. [Proxied records](/dns/manage-dns-records/reference/proxied-dns-records/#proxied-records) are flattened by default as they return Cloudflare anycast IPs. @@ -45,15 +45,15 @@ Make a `PATCH` request to the [Update DNS Settings](/api/resources/dns/subresour ## Per record -Paid zones also have the option of flattening specific `CNAME` records. +Paid zones also have the option of flattening specific CNAME records. -If you use this option, a special [tag](/dns/manage-dns-records/reference/record-attributes/) `cf-flatten-cname` will be added to the respective flattened `CNAME` records in your zone file, allowing you to [export and import records](/dns/manage-dns-records/how-to/import-and-export/) without losing this configuration. +If you use this option, a special [tag](/dns/manage-dns-records/reference/record-attributes/) `cf-flatten-cname` will be added to the respective flattened CNAME records in your zone file, allowing you to [export and import records](/dns/manage-dns-records/how-to/import-and-export/) without losing this configuration. 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. +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. @@ -66,7 +66,7 @@ For the following cases, **Flatten** will not be available: -With the available [API endpoints](/api/resources/dns/subresources/records/methods/create/), specify the following for each `CNAME` record in the request body: +With the available [API endpoints](/api/resources/dns/subresources/records/methods/create/), specify the following for each CNAME record in the request body: ```txt "settings": { diff --git a/src/content/docs/dns/dns-firewall/index.mdx b/src/content/docs/dns/dns-firewall/index.mdx index eaaaa74e55a83e6..bf8ea2038e8cd4f 100644 --- a/src/content/docs/dns/dns-firewall/index.mdx +++ b/src/content/docs/dns/dns-firewall/index.mdx @@ -10,7 +10,7 @@ import { Description, Plan } from "~/components" -Speed up and protect entire authoritative nameservers +Speed up and protect entire authoritative nameservers @@ -19,7 +19,7 @@ Cloudflare DNS Firewall proxies all DNS queries to your nameservers through Clou ![Diagram showing protection provided by DNS Firewall. For more details, read further.](~/assets/images/dns/dns-firewall-overview.png) -DNS Firewall is for customers who need to speed up and protect entire authoritative nameservers. If you need to speed up and protect individual zones, see Cloudflare DNS [Zone Setups](/dns/zone-setups). +DNS Firewall is for customers who need to speed up and protect entire authoritative nameservers. If you need to speed up and protect individual zones, refer to Cloudflare DNS [Setups](/dns/zone-setups/). *** diff --git a/src/content/docs/dns/dnssec/dnssec-states.mdx b/src/content/docs/dns/dnssec/dnssec-states.mdx index be03ff37ec5b55a..dbd891fd9baba09 100644 --- a/src/content/docs/dns/dnssec/dnssec-states.mdx +++ b/src/content/docs/dns/dnssec/dnssec-states.mdx @@ -18,13 +18,13 @@ This page describes different DNSSEC states and how they relate to the responses :::caution -Once you have enabled DNSSEC on a zone for the first time, you cannot transition directly from an `active` state to a `deleted` state. You can only [delete DNSSEC records](/api/resources/dns/subresources/dnssec/methods/delete/) once your zone DNSSEC is in a `disabled` state. Cloudflare prevents you from deleting DNSSEC records before removing the DS record from the registrar to avoid DNS resolution issues. +Once you have enabled DNSSEC on a zone for the first time, you cannot transition directly from an `active` state to a `deleted` state. You can only [delete DNSSEC records](/api/resources/dns/subresources/dnssec/methods/delete/) once your zone DNSSEC is in a `disabled` state. Cloudflare prevents you from deleting DNSSEC records before removing the DS record from the registrar to avoid DNS resolution issues. ::: -In both `pending` and `active` states, Cloudflare signs the zone and responds with `RRSIG`, `NSEC`, `DNSKEY`, `CDS`, and `CDNSKEY` record types. +In both `pending` and `active` states, Cloudflare signs the zone and responds with RRSIG, NSEC, DNSKEY, CDS, and CDNSKEY record types. -In `pending-disabled` and `disabled` states, Cloudflare still signs the zone and serves `RRSIG`, `NSEC`, and `DNSKEY` record types, but the `CDS` and `CDNSKEY` records are set to zero ([RFC 8078](https://www.rfc-editor.org/rfc/rfc8078.html#section-4)), signaling to the registrar that DNSSEC should be disabled. +In `pending-disabled` and `disabled` states, Cloudflare still signs the zone and serves RRSIG, NSEC, and DNSKEY record types, but the CDS and CDNSKEY records are set to zero ([RFC 8078](https://www.rfc-editor.org/rfc/rfc8078.html#section-4)), signaling to the registrar that DNSSEC should be disabled. -In `deleted` state, Cloudflare does **not** sign the zone and does **not** respond with `RRSIG`, `NSEC`, `DNSKEY`, `CDS`, and `CDNSKEY` record types. +In `deleted` state, Cloudflare does **not** sign the zone and does **not** respond with RRSIG, NSEC, DNSKEY, CDS, and CDNSKEY record types. Refer to [How DNSSEC works](https://www.cloudflare.com/dns/dnssec/how-dnssec-works/) to learn more about the authentication process and records involved. 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 421f500ab86e2e0..247db8ef6576456 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 @@ -30,9 +30,9 @@ These records include the following fields: :::note - Cloudflare uses the [canonical notation](https://www.rfc-editor.org/rfc/rfc5952.html#section-4.2) to store DNS records. This means that an `AAAA` record with content `fe80::0:0:1` is stored and returned as `fe80::1`, for example. + Cloudflare uses the [canonical notation](https://www.rfc-editor.org/rfc/rfc5952.html#section-4.2) to store DNS records. This means that an AAAA record with content `fe80::0:0:1` is stored and returned as `fe80::1`, for example. - Alternative notations of IPv4 addresses (`1.1` for `1.0.0.1`, for example) are not supported for `A` records. + Alternative notations of IPv4 addresses (`1.1` for `1.0.0.1`, for example) are not supported for A records. ::: * **TTL**: Time to live, which controls how long DNS resolvers should cache a response before revalidating it. @@ -42,9 +42,9 @@ These records include the following fields: #### Example API call -When creating `A` or `AAAA` records [using the API](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records): +When creating A or AAAA records [using the API](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records): -* The `content` of the records is an IP address (IPv4 for `A` or IPv6 for `AAAA`). +* The `content` of the records is an IP address (IPv4 for A or IPv6 for AAAA). * The `proxied` field affects the record's [proxy status](/dns/manage-dns-records/reference/proxied-dns-records/). @@ -109,13 +109,13 @@ These records include the following fields: * If the **Proxy Status** is **DNS Only**, you can customize the value. * **Proxy status**: For more details, refer to [Proxied DNS records](/dns/manage-dns-records/reference/proxied-dns-records/). -You can use `CNAME` records to point to other `CNAME` records (`www.example2.com` --> `www.example1.com` --> `www.example.com`), but the final record must point to a hostname with a valid IP address (and therefore a valid `A` or `AAAA` record) if this hostname is meant to proxy traffic. +You can use CNAME records to point to other CNAME records (`www.example2.com` --> `www.example1.com` --> `www.example.com`), but the final record must point to a hostname with a valid IP address (and therefore a valid A or AAAA record) if this hostname is meant to proxy traffic. -Cloudflare uses a process called `CNAME` flattening to deliver better performance. This process supports a few features and can interact with [different setups that depend on `CNAME` records](/dns/cname-flattening/#aspects-to-keep-in-mind). Refer to the [`CNAME` flattening section](/dns/cname-flattening/) to learn more about this. +Cloudflare uses a process called CNAME flattening to deliver better performance. This process supports a few features and can interact with [different setups that depend on CNAME records](/dns/cname-flattening/#aspects-to-keep-in-mind). Refer to the [CNAME flattening section](/dns/cname-flattening/) to learn more about this. #### Example API call -When creating `CNAME` records [using the API](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records): +When creating CNAME records [using the API](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records): * The `content` of the records is a [fully qualified domain name](https://en.wikipedia.org/wiki/Fully_qualified_domain_name). * The `proxied` field affects the record's [proxy status](/dns/manage-dns-records/reference/proxied-dns-records/) diff --git a/src/content/docs/dns/manage-dns-records/reference/wildcard-dns-records.mdx b/src/content/docs/dns/manage-dns-records/reference/wildcard-dns-records.mdx index 454e4a33c2ad1b0..0fa4686e87ea217 100644 --- a/src/content/docs/dns/manage-dns-records/reference/wildcard-dns-records.mdx +++ b/src/content/docs/dns/manage-dns-records/reference/wildcard-dns-records.mdx @@ -74,7 +74,7 @@ Customers on all plans can create and proxy wildcard DNS records. ## Limitations -If you are using a [partial zone setup](/dns/zone-setups/partial-setup/) for your DNS, Cloudflare does not automatically provision SSL/TLS certificates for your wildcard record. +If you are using a [partial (CNAME) setup](/dns/zone-setups/partial-setup/) for your DNS, Cloudflare does not automatically provision SSL/TLS certificates for your wildcard record. diff --git a/src/content/docs/dns/manage-dns-records/troubleshooting/records-with-same-name.mdx b/src/content/docs/dns/manage-dns-records/troubleshooting/records-with-same-name.mdx index 52a8118fa9fc728..3af3f57f6bac129 100644 --- a/src/content/docs/dns/manage-dns-records/troubleshooting/records-with-same-name.mdx +++ b/src/content/docs/dns/manage-dns-records/troubleshooting/records-with-same-name.mdx @@ -13,16 +13,16 @@ import { Render } from "~/components" Occasionally, Cloudflare will not allow you to [create new DNS records](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) with the same value in the **Name** field. -This error can occur due to the special requirements of `CNAME` records[^1]. +This error can occur due to the special requirements of CNAME records[^1]. ## Causes You will encounter this error if you try to do one of the following: -* Create a `CNAME` record with a **Name** matching the name of an existing `A`/`AAAA`[^2] or `CNAME` record. -* Create an `A`/`AAAA` record with a **Name** matching the name of an existing `CNAME` record. +* Create a CNAME record with a **Name** matching the name of an existing A/AAAA[^2] or CNAME record. +* Create an A/AAAA record with a **Name** matching the name of an existing CNAME record. -Cloudflare prevents you from creating this combination of records because if a `CNAME` record is provided for a hostname DNS servers expect only that `CNAME` record to provide DNS information for that hostname. +Cloudflare prevents you from creating this combination of records because if a CNAME record is provided for a hostname DNS servers expect only that CNAME record to provide DNS information for that hostname. Adding additional records would send conflicting information to DNS servers. For a technical explanation of the mechanism behind this, refer to [RFC 1034](https://www.rfc-editor.org/rfc/rfc1034). @@ -33,7 +33,7 @@ Review your existing DNS records to find the matching value in the **Name** fiel :::note -`CNAME` records are the only IP resolution record with this type of limitation. You can have more than one `A`/`AAAA` record per hostname, which is a way some domains do [simple load balancing](/dns/manage-dns-records/how-to/round-robin-dns/) for incoming requests. +CNAME records are the only IP resolution record with this type of limitation. You can have more than one A/AAAA record per hostname, which is a way some domains do [simple load balancing](/dns/manage-dns-records/how-to/round-robin-dns/) for incoming requests. ::: diff --git a/src/content/docs/dns/troubleshooting/dns-issues.mdx b/src/content/docs/dns/troubleshooting/dns-issues.mdx index b5ce4b03062ff3e..7feab42138c3877 100644 --- a/src/content/docs/dns/troubleshooting/dns-issues.mdx +++ b/src/content/docs/dns/troubleshooting/dns-issues.mdx @@ -30,7 +30,7 @@ Ensure that you have the necessary DNS records in the **DNS** app of your Clou :::note -If you have a [partial zone setup](/dns/zone-setups/partial-setup), ensure your DNS records also exist in your authoritative nameservers. +If you have a [partial (CNAME) setup](/dns/zone-setups/partial-setup), ensure your DNS records also exist in your authoritative nameservers. ::: ### DNSSEC was not disabled before the domain was added to Cloudflare diff --git a/src/content/docs/dns/zone-setups/conversions/index.mdx b/src/content/docs/dns/zone-setups/conversions/index.mdx index ffa8fa025f1cdf0..fa458adee27072e 100644 --- a/src/content/docs/dns/zone-setups/conversions/index.mdx +++ b/src/content/docs/dns/zone-setups/conversions/index.mdx @@ -1,15 +1,15 @@ --- pcx_content_type: navigation -title: Zone setup conversions +title: DNS setup conversions sidebar: order: 10 group: hideIndex: true - label: Zone conversions + label: Setup conversions --- import { DirectoryListing } from "~/components"; -You can perform the following zone setup conversions: +You can perform the following DNS setup conversions: \ No newline at end of file diff --git a/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx b/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx index fbcae2b873a6021..9a8bf3240f13069 100644 --- a/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx +++ b/src/content/docs/dns/zone-setups/partial-setup/dns-resolution.mdx @@ -15,7 +15,7 @@ When you have a - The `CNAME` record for `www.example.com` would be: + The CNAME record for `www.example.com` would be: ```txt www.example.com CNAME www.example.com.cdn.cloudflare.net @@ -88,7 +88,7 @@ If your organization has multiple Cloudflare accounts, also consider using zone - 2. Remove any previously existing `A`, `AAAA`, or `CNAME` records referencing the hostnames you want to proxy through Cloudflare. For these hostnames, leave only the records pointing to `{your-hostname}.cdn.cloudflare.net`. + 2. Remove any previously existing A, AAAA, or CNAME records referencing the hostnames you want to proxy through Cloudflare. For these hostnames, leave only the records pointing to `{your-hostname}.cdn.cloudflare.net`. 2. Repeat this process for each subdomain that should be proxied to Cloudflare. diff --git a/src/content/docs/dns/zone-setups/reference/index.mdx b/src/content/docs/dns/zone-setups/reference/index.mdx index 9ecb5af8d5c3056..f9009d7fbc0faeb 100644 --- a/src/content/docs/dns/zone-setups/reference/index.mdx +++ b/src/content/docs/dns/zone-setups/reference/index.mdx @@ -7,7 +7,7 @@ sidebar: hideIndex: true head: - tag: title - content: Reference — Zone setups + content: Reference — DNS zone setups --- 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 1d327b645a9cdd6..8382a4194ef4348 100644 --- a/src/content/docs/dns/zone-setups/subdomain-setup/dnssec.mdx +++ b/src/content/docs/dns/zone-setups/subdomain-setup/dnssec.mdx @@ -22,12 +22,12 @@ Ideally, you should also wait 12 to 24 hours after enabling DNSSEC on the parent 2. Make sure the child zone is [active](/dns/zone-setups/reference/domain-status/) on Cloudflare and that DNS resolution is working properly for your subdomain. -3. [Enable DNSSEC](/dns/dnssec/) for the child zone and save the information provided within the `DS` record output. +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. 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. ![Screenshot showing how to add a DS record within Cloudflare](~/assets/images/dns/ds-record-example.png) -5. Add an `A` record to the child zone to validate DNS resolution. +5. Add an A record to the child zone to validate DNS resolution. -6. Wait two to six hours. Then, [test the `A` record](/dns/dnssec/troubleshooting/#test-dnssec-with-dig) added in the previous step using multiple DNS resolvers with DNSSEC validation (`1.1.1.1`, `8.8.8.8`, and `9.9.9.9`). For example, if the `A` record is for `test.child.example.com`: `dig test.child.example.com +dnssec @1.1.1.1`. +6. Wait two to six hours. Then, [test the A record](/dns/dnssec/troubleshooting/#test-dnssec-with-dig) added in the previous step using multiple DNS resolvers with DNSSEC validation (`1.1.1.1`, `8.8.8.8`, and `9.9.9.9`). For example, if the A record is for `test.child.example.com`: `dig test.child.example.com +dnssec @1.1.1.1`. 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 5003bcc060b681a..e6ef6e8ae884eb9 100644 --- a/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx +++ b/src/content/docs/dns/zone-setups/subdomain-setup/rollback.mdx @@ -18,7 +18,7 @@ Refer to the following process to understand how you can rollback a [subdomain s :::caution[Important] -This process may incur in downtime, as it is not possible to add address records (`A`/`AAAA`) while still having [corresponding `NS` records at the same name](/dns/manage-dns-records/troubleshooting/existing-ns-record/) within the parent zone. +This process may incur in downtime, as it is not possible to add address records (A/AAAA) while still having [corresponding NS records at the same name](/dns/manage-dns-records/troubleshooting/existing-ns-record/) within the parent zone. ::: ## Steps diff --git a/src/content/docs/dns/zone-setups/subdomain-setup/setup/index.mdx b/src/content/docs/dns/zone-setups/subdomain-setup/setup/index.mdx index 10114b4e8edd675..60ceac074cc19db 100644 --- a/src/content/docs/dns/zone-setups/subdomain-setup/setup/index.mdx +++ b/src/content/docs/dns/zone-setups/subdomain-setup/setup/index.mdx @@ -16,7 +16,7 @@ import { DirectoryListing, GlossaryTooltip, Render } from "~/components" Subdomain setup is only available for Enterprise accounts. If you only want to create a subdomain for your site in Cloudflare, refer to [Create a subdomain record](/dns/manage-dns-records/how-to/create-subdomain/). ::: -[Subdomain setup](/dns/zone-setups/subdomain-setup/) relies on a process known as delegation. When, in a parent domain such as `example.com`, an [`NS` record](https://www.cloudflare.com/learning/dns/dns-records/dns-ns-record/) is created for a subdomain `blog.example.com`, this means that DNS management for the subdomain can be done separately, in its own DNS zone. +[Subdomain setup](/dns/zone-setups/subdomain-setup/) relies on a process known as delegation. When, in a parent domain such as `example.com`, an [NS record](https://www.cloudflare.com/learning/dns/dns-records/dns-ns-record/) is created for a subdomain `blog.example.com`, this means that DNS management for the subdomain can be done separately, in its own DNS zone. ```mermaid flowchart TD diff --git a/src/content/docs/dns/zone-setups/troubleshooting/index.mdx b/src/content/docs/dns/zone-setups/troubleshooting/index.mdx index b53b6641bbb960c..a3055433fe60b91 100644 --- a/src/content/docs/dns/zone-setups/troubleshooting/index.mdx +++ b/src/content/docs/dns/zone-setups/troubleshooting/index.mdx @@ -7,7 +7,7 @@ sidebar: hideIndex: true head: - tag: title - content: Troubleshooting — Zone setups + content: Troubleshooting — DNS setups --- 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 3278794858803d7..187e6b1cb475958 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 @@ -16,12 +16,12 @@ With [outgoing zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-pri ### DNS-only CNAME records -As explained in [DNS record types](/dns/manage-dns-records/reference/dns-record-types/#cname), Cloudflare uses a process called [`CNAME` flattening](/dns/cname-flattening/) to return the final IP address instead of the `CNAME` target. `CNAME` flattening improves performance and is also what allows you to set a `CNAME` record on the zone apex. +As explained in [DNS record types](/dns/manage-dns-records/reference/dns-record-types/#cname), Cloudflare uses a process called [CNAME flattening](/dns/cname-flattening/) to return the final IP address instead of the CNAME target. CNAME flattening improves performance and is also what allows you to set a CNAME record on the zone apex. -Depending on the [settings](/dns/cname-flattening/set-up-cname-flattening/) you have, when you use DNS-only `CNAME` records with outgoing zone transfers, you can expect the following: +Depending on the [settings](/dns/cname-flattening/set-up-cname-flattening/) you have, when you use DNS-only CNAME records with outgoing zone transfers, you can expect the following: -- For DNS-only `CNAME` records on the zone apex, Cloudflare will always transfer out the flattened IP addresses. -- For DNS-only `CNAME` records on subdomains, Cloudflare will only transfer out flattened IP addresses if the setting [**Flatten all CNAMEs**](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records) is enabled. +- For DNS-only CNAME records on the zone apex, Cloudflare will always transfer out the flattened IP addresses. +- For DNS-only CNAME records on subdomains, Cloudflare will only transfer out flattened IP addresses if the setting [**Flatten all CNAMEs**](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records) is enabled. ### Proxied records @@ -118,9 +118,9 @@ It should also have updated [Access Control Lists (ACLs)](/dns/zone-setups/zone- ## 5. Add secondary nameservers within Cloudflare -Using the information from your secondary DNS provider, [create `NS` records](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) on your zone apex listing your secondary nameservers. +Using the information from your secondary DNS provider, [create NS records](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) on your zone apex listing your secondary nameservers. -By default, Cloudflare ignores `NS` records added to the zone apex. To modify this behavior, enable [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns): +By default, Cloudflare ignores NS records added to the zone apex. To modify this behavior, enable [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns): :::note If your account [zone defaults](/dns/additional-options/dns-zone-defaults/) are already defined to have **Multi-provider DNS** enabled, this step may not be necessary. 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 984091633d8fc67..7a420a0bd0435dd 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 @@ -12,11 +12,11 @@ import { TabItem, Tabs } 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. -With Secondary DNS override, you can use Cloudflare as your secondary DNS provider but still get the [performance and security benefits](/learning-paths/get-started/concepts/how-cloudflare-works/#benefits) of Cloudflare's proxy. Additionally it lets you override any `A` and `AAAA` records on your zone apex with a `CNAME` record. +With Secondary DNS override, you can use Cloudflare as your secondary DNS provider but still get the [performance and security benefits](/learning-paths/get-started/concepts/how-cloudflare-works/#benefits) of Cloudflare's proxy. Additionally it lets you override any A and AAAA records on your zone apex with a CNAME record. :::note -Only `A`, `AAAA`, and `CNAME` records can be proxied. +Only A, AAAA, and CNAME records can be proxied. ::: @@ -41,7 +41,7 @@ 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, [change](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records) their **Proxy status** to **Proxied**. +4. On **DNS** > **Records**, for specific A, AAAA, or CNAME records, [change](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records) their **Proxy status** to **Proxied**. @@ -58,20 +58,20 @@ https://api.cloudflare.com/client/v4/zones/{zone_id}/dns_settings \ }' ``` -2. For specific `A`, `AAAA`, or `CNAME` records, send a [POST](/api/resources/dns/subresources/records/methods/create/) request with the `proxied` status as `true`. +2. For specific A, AAAA, or CNAME records, send a [POST](/api/resources/dns/subresources/records/methods/create/) request with the `proxied` status as `true`. - Make sure the added record has the same name as the transferred record you intend to proxy. Cloudflare only looks at the name and the proxy status, so the record content does not matter. -## Proxied `A` and `AAAA` records +## Proxied A and AAAA records -After proxying (orange clouding) a Secondary DNS record, any additional records under that hostname transferred from the primary DNS provider are automatically proxied. This applies to all `A` and `AAAA` records under that domain. +After proxying (orange clouding) a Secondary DNS record, any additional records under that hostname transferred from the primary DNS provider are automatically proxied. This applies to all A and AAAA records under that domain. -## `CNAME` record on the zone apex +## CNAME record on the zone apex -You can also add a `CNAME` record on the zone apex (supported through [CNAME Flattening](/dns/cname-flattening/)) and either proxy that record or keep it on DNS Only. +You can also add a CNAME record on the zone apex (supported through [CNAME Flattening](/dns/cname-flattening/)) and either proxy that record or keep it on DNS Only. -Once you create a `CNAME` record at the apex, existing `A` or `AAAA` records on the zone apex will be deactivated. You can view those deactivated records by clicking **View Inactive Records**. To re-activate the `A` or `AAAA` records at the root, remove the `CNAME` record. +Once you create a CNAME record at the apex, existing A or AAAA records on the zone apex will be deactivated. You can view those deactivated records by clicking **View Inactive Records**. To re-activate the A or AAAA records at the root, remove the CNAME record. ## Verify that your records are proxied diff --git a/src/content/docs/fundamentals/setup/use-cloudflare-without-changing-nameservers.mdx b/src/content/docs/fundamentals/setup/use-cloudflare-without-changing-nameservers.mdx index 229720e30ddd576..02682fa71adb9c9 100644 --- a/src/content/docs/fundamentals/setup/use-cloudflare-without-changing-nameservers.mdx +++ b/src/content/docs/fundamentals/setup/use-cloudflare-without-changing-nameservers.mdx @@ -9,4 +9,4 @@ sidebar: If you cannot [change your domain nameservers](/dns/zone-setups/full-setup/), you can still use Cloudflare on your website by: * Activating Cloudflare through a [certified hosting partner](https://www.cloudflare.com/hosting-partners). -* Using a [partial zone setup](/dns/zone-setups/partial-setup/). +* Using a [partial (CNAME) setup](/dns/zone-setups/partial-setup/). diff --git a/src/content/docs/ssl/edge-certificates/troubleshooting/caa-records.mdx b/src/content/docs/ssl/edge-certificates/troubleshooting/caa-records.mdx index 23dd7d0883769d3..7dec27b8be865cd 100644 --- a/src/content/docs/ssl/edge-certificates/troubleshooting/caa-records.mdx +++ b/src/content/docs/ssl/edge-certificates/troubleshooting/caa-records.mdx @@ -7,7 +7,7 @@ title: Certification Authority Authorization (CAA) FAQ import { Render } from "~/components" -The following page answers common questions about Certification Authority Authorization (`CAA`) records. +The following page answers common questions about Certification Authority Authorization (CAA) records. *** @@ -21,11 +21,11 @@ For more details, refer to [Create CAA records](/ssl/edge-certificates/caa-recor ## How does Cloudflare evaluate CAA records? -`CAA` records are evaluated by a CA, not by Cloudflare. +CAA records are evaluated by a CA, not by Cloudflare. :::note -Setting a `CAA` record to specify one or more particular CAs does not affect which CA(s) Cloudflare uses to issue a Universal or Advanced SSL certificate for your domain. +Setting a CAA record to specify one or more particular CAs does not affect which CA(s) Cloudflare uses to issue a Universal or Advanced SSL certificate for your domain. You can specify CAs associated with Cloudflare certificates when [ordering an advanced certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/). @@ -36,7 +36,7 @@ You can specify CAs associated with Cloudflare certificates when [ordering an ad ## What are the dangers of setting CAA records? -If you are part of a large organization or one where multiple parties are tasked with obtaining SSL certificates, [include `CAA` records](/ssl/edge-certificates/caa-records/) that allow issuance for all CAs applicable for your organization. Failure to do so can inadvertently block SSL issuance for other parts of your organization. +If you are part of a large organization or one where multiple parties are tasked with obtaining SSL certificates, [include CAA records](/ssl/edge-certificates/caa-records/) that allow issuance for all CAs applicable for your organization. Failure to do so can inadvertently block SSL issuance for other parts of your organization. *** diff --git a/src/content/partials/dns/cname-flattening-callout.mdx b/src/content/partials/dns/cname-flattening-callout.mdx index f94820dde836d51..030fec534c89c49 100644 --- a/src/content/partials/dns/cname-flattening-callout.mdx +++ b/src/content/partials/dns/cname-flattening-callout.mdx @@ -3,4 +3,4 @@ --- -If a `CNAME` target is being used to verify a domain for a third-party service, turning on [CNAME flattening for all CNAME records](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records) may cause the verification to fail since the `CNAME` record itself will not be returned directly. +If a CNAME target is being used to verify a domain for a third-party service, turning on [CNAME flattening for all CNAME records](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records) may cause the verification to fail since the CNAME record itself will not be returned directly.