From f6791bab42a496cd4dc5bf4d44a2236dfb4175f9 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Tue, 12 Nov 2024 14:10:58 +0000 Subject: [PATCH 1/3] Add AWS Amplify to vendor-specific-records --- .../reference/vendor-specific-records.mdx | 41 +++++++++++++++---- 1 file changed, 34 insertions(+), 7 deletions(-) diff --git a/src/content/docs/dns/manage-dns-records/reference/vendor-specific-records.mdx b/src/content/docs/dns/manage-dns-records/reference/vendor-specific-records.mdx index 82920bd8c2bd5d2..5afa995bf43ec9d 100644 --- a/src/content/docs/dns/manage-dns-records/reference/vendor-specific-records.mdx +++ b/src/content/docs/dns/manage-dns-records/reference/vendor-specific-records.mdx @@ -5,9 +5,9 @@ title: Vendor-specific DNS records --- -import { Render } from "~/components" +import { Render, GlossaryTooltip, Example } from "~/components" -This article requires prior knowledge of DNS record management via the Cloudflare dashboard. To learn more, refer to Cloudflare's article on [managing DNS records](/dns/manage-dns-records/how-to/create-dns-records/). +This article requires prior knowledge of DNS record management via the Cloudflare dashboard. To learn more, refer to Cloudflare's article on [managing DNS records](/dns/manage-dns-records/how-to/create-dns-records/). ## Google @@ -46,7 +46,7 @@ AWS customers must [update their domain's nameservers](https://docs.aws.amazon.c Find the [URL](https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-bucket-intro.html) for your bucket. -Then, [create a `CNAME` record](/dns/manage-dns-records/how-to/create-dns-records/) in Cloudflare. For example, if the full host URL of the bucket is `files.example.com.s3.amazonaws.com`, you would add a `CNAME` record similar to the following: +Then, [create a `CNAME` record](/dns/manage-dns-records/how-to/create-dns-records/) in Cloudflare. For example, if the full host URL of the bucket is `files.example.com.s3.amazonaws.com`, you would add a `CNAME` record similar to the following: ```txt files CNAME files.example.com.s3.amazonaws.com @@ -58,14 +58,41 @@ For help setting up DKIM in SES, refer to the [Amazon documentation](https://doc ### Amazon ELB configuration -Refer to [Amazon's ELB help content](http://docs.amazonwebservices.com/ElasticLoadBalancing/latest/DeveloperGuide/using-domain-names-with-elb.html) for guidance on ELB configuration at Amazon, but generally you should: +Refer to [Amazon's ELB help content](http://docs.amazonwebservices.com/ElasticLoadBalancing/latest/DeveloperGuide/using-domain-names-with-elb.html) for guidance on ELB configuration at Amazon, but generally you should: -Add a [`CNAME` record](/dns/manage-dns-records/how-to/create-dns-records/) to Cloudflare for the hostname you receive from AWS, for example: +Add a [`CNAME` record](/dns/manage-dns-records/how-to/create-dns-records/) to Cloudflare for the hostname you receive from AWS, for example: + | Type | Name | Target | Proxy status | | ------- | ----- | -------------------------------------------- | ------------ | | `CNAME` | `elb` | `.._elb.amazonaws.com` | Proxied | + +### Amazon Amplify + +To use Cloudflare DNS with AWS Amplify, refer to the [Amplify help content](https://docs.aws.amazon.com/amplify/latest/userguide/to-add-a-custom-domain-managed-by-a-third-party-dns-provider.html) and follow the instructions for **manual configuration**. + +You will need at least two `CNAME` records: + +- A DNS-only `CNAME` to validate your domain ownership, which should look like the following: + + +| Type | Name | Target | Proxy status | Flatten | +| ------- | ----- | -------------------------------------------- | ------------ |---------| +| `CNAME` | `.example.com` | `.mhbtsbpdnt.acm-validation.aws` | DNS only | False | + + +:::caution + +::: + +- One `CNAME` for the apex domain and/or for each of the subdomains that you want to proxy through Cloudflare. + + +| Type | Name | Target | +| ------- | ----- | -------------------------------------------- | +| `CNAME` | `blog` | `.cloudfront.net` | + *** ## Microsoft @@ -76,9 +103,9 @@ For information about the records to Microsoft 365, refer to [Microsoft's docume ### Microsoft Azure -Follow Microsoft’s instructions on [configuring Azure DNS settings](https://learn.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-domain). +Follow Microsoft's instructions on [configuring Azure DNS settings](https://learn.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-domain). -Then, add Azure’s required records to [Cloudflare DNS](/dns/manage-dns-records/how-to/create-dns-records/). +Then, add Azure's required records to [Cloudflare DNS](/dns/manage-dns-records/how-to/create-dns-records/). *** From e0b3b10eb183c6d4cf9bf44d517484cf9f1928b8 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Tue, 12 Nov 2024 14:56:32 +0000 Subject: [PATCH 2/3] Improve records examples and consolidate Flattening callouts --- .../reference/vendor-specific-records.mdx | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/src/content/docs/dns/manage-dns-records/reference/vendor-specific-records.mdx b/src/content/docs/dns/manage-dns-records/reference/vendor-specific-records.mdx index 5afa995bf43ec9d..4fc63d9f8df47ee 100644 --- a/src/content/docs/dns/manage-dns-records/reference/vendor-specific-records.mdx +++ b/src/content/docs/dns/manage-dns-records/reference/vendor-specific-records.mdx @@ -72,23 +72,28 @@ Add a [`CNAME` record](/dns/manage-dns-records/how-to/create-dns-records/) to Cl To use Cloudflare DNS with AWS Amplify, refer to the [Amplify help content](https://docs.aws.amazon.com/amplify/latest/userguide/to-add-a-custom-domain-managed-by-a-third-party-dns-provider.html) and follow the instructions for **manual configuration**. -You will need at least two `CNAME` records: +At Cloudflare, you will need at least two `CNAME` records: - A DNS-only `CNAME` to validate your domain ownership, which should look like the following: -| Type | Name | Target | Proxy status | Flatten | -| ------- | ----- | -------------------------------------------- | ------------ |---------| -| `CNAME` | `.example.com` | `.mhbtsbpdnt.acm-validation.aws` | DNS only | False | +| Type | Name | Target | Proxy status | +| ------- | ----- | -------------------------------------------- | ------------ | +| `CNAME` | `` | `.mhbtsbpdnt.acm-validation.aws` | DNS only | -:::caution - +:::caution[CNAME flattening] +If your Cloudflare zone is on a paid plan, also make sure that the **Flatten** option turned off for the validation `CNAME` record, and that you zone is **not** using [CNAME flattening for all CNAME records](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records) ::: -- One `CNAME` for the apex domain and/or for each of the subdomains that you want to proxy through Cloudflare. +- One `CNAME` for the apex domain (`example.com`) and/or for each of the subdomains (`blog.example.com`) that you want to manage on Cloudflare. For details refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/). These records can be proxied. + +| Type | Name | Target | +| ------- | ----- | -------------------------------------------- | +| `CNAME` | `@` | `.cloudfront.net` | + | Type | Name | Target | | ------- | ----- | -------------------------------------------- | | `CNAME` | `blog` | `.cloudfront.net` | From e3b5ccc88435881ea8c57ea4b58e203ebe794379 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro <62246989+RebeccaTamachiro@users.noreply.github.com> Date: Thu, 14 Nov 2024 09:29:36 +0000 Subject: [PATCH 3/3] Apply suggestion from code review Co-authored-by: Jun Lee --- .../manage-dns-records/reference/vendor-specific-records.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/dns/manage-dns-records/reference/vendor-specific-records.mdx b/src/content/docs/dns/manage-dns-records/reference/vendor-specific-records.mdx index 4fc63d9f8df47ee..18b72458507f29c 100644 --- a/src/content/docs/dns/manage-dns-records/reference/vendor-specific-records.mdx +++ b/src/content/docs/dns/manage-dns-records/reference/vendor-specific-records.mdx @@ -83,7 +83,7 @@ At Cloudflare, you will need at least two `CNAME` records: :::caution[CNAME flattening] -If your Cloudflare zone is on a paid plan, also make sure that the **Flatten** option turned off for the validation `CNAME` record, and that you zone is **not** using [CNAME flattening for all CNAME records](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records) +If your Cloudflare zone is on a paid plan, also make sure that the **Flatten** option turned off for the validation `CNAME` record, and that you zone is **not** using [CNAME flattening for all CNAME records](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records). ::: - One `CNAME` for the apex domain (`example.com`) and/or for each of the subdomains (`blog.example.com`) that you want to manage on Cloudflare. For details refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/). These records can be proxied.