diff --git a/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx b/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx index 1f01a1d142a3db..abd295dcf2760c 100644 --- a/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx +++ b/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx @@ -14,7 +14,7 @@ Use this setup for simple, [round-robin load balancing](https://www.cloudflare.c The following example illustrates how you would distribute traffic intended for `www.example.com`. Though the example uses `A` records, you could also use `AAAA` records. -After [creating an account](/fundamentals/account/create-account/) and [updating your nameservers](/dns/zone-setups/full-setup/setup/) for `example.com`, you might [create multiple DNS records](/dns/manage-dns-records/how-to/create-dns-records/) for your `www` subdomain: +After [creating an account](/fundamentals/account/create-account/) and [updating your nameservers](/dns/zone-setups/full-setup/setup/) for `example.com`, you might [create multiple subdomain DNS records](/dns/manage-dns-records/how-to/create-dns-records/) for `www`: | Type | Name | IPv4 address | | ---- | ----- | ------------ | diff --git a/src/content/docs/fundamentals/manage-domains/redirect-domain.mdx b/src/content/docs/fundamentals/manage-domains/redirect-domain.mdx index 0dc0c845482236..cc7e2274adfcaf 100644 --- a/src/content/docs/fundamentals/manage-domains/redirect-domain.mdx +++ b/src/content/docs/fundamentals/manage-domains/redirect-domain.mdx @@ -9,7 +9,7 @@ If you have an alias domain that only forwards traffic to another domain (that i 1. [Add](/fundamentals/manage-domains/#add-a-domain-to-cloudflare) your alias domain (for example, `previous.com`) to Cloudflare. -2. Make sure that your alias domain has a proxied [DNS A or CNAME record](/dns/manage-dns-records/how-to/create-dns-records/) that properly resolves DNS queries. You may also want to include a record for the `www` subdomain. +2. Make sure that your alias domain has a proxied [DNS A or CNAME record](/dns/manage-dns-records/how-to/create-dns-records/) that properly resolves DNS queries. You may also want to include a subdomain DNS record for `www`. Use the IP address `192.0.2.1` for the `A` record. This address does not route traffic to an origin server but allows Cloudflare to apply rules, redirects, and Workers to incoming traffic. The equivalent IP address for an `AAAA` record is `100::`. diff --git a/src/content/partials/dns/create-subdomain-record.mdx b/src/content/partials/dns/create-subdomain-record.mdx index 7438c590167c29..45f7c7c80f75c1 100644 --- a/src/content/partials/dns/create-subdomain-record.mdx +++ b/src/content/partials/dns/create-subdomain-record.mdx @@ -7,13 +7,13 @@ import { Example, Render } from "~/components"; Most subdomains serve a specific purpose within the overall context of your website. For example, `blog.example.com` might be your blog, `support.example.com` could be your customer help portal, and `store.example.com` would be your e-commerce site. -Even if you do not require specific subdomains, you might want to set up at least the `www` subdomain. It will usually point to the same content as what you have on the apex domain (`example.com`) or use a [redirect](/fundamentals/manage-domains/manage-subdomains/#redirect-a-subdomain-to-the-apex-domain). Having a DNS record on the `www` subdomain helps guarantee that a visitor who types `www.` in front of your domain address on their browser can still find your website or application. +Even if you do not require specific subdomains, you might want to set up at least a subdomain record on `www`. It will usually point to the same content as what you have on the apex domain (`example.com`) or use a [redirect](/fundamentals/manage-domains/manage-subdomains/#redirect-a-subdomain-to-the-apex-domain). Having a subdomain DNS record on `www` helps guarantee that a visitor who types `www.` in front of your domain address can still find your website or application. ## Subdomain records -To create a new subdomain, you would first add the subdomain content at your [host](/fundamentals/manage-domains/#host-your-domain). +To host content on a subdomain of your domain, first ensure that your [hosting provider](/fundamentals/manage-domains/#host-your-domain) can serve content for the given hostname (`.example.com`). -Then, you would create a corresponding [IP address resolution record](/dns/manage-dns-records/reference/dns-record-types/#ip-address-resolution) (`A`, `AAAA`, or `CNAME`), specifying the subdomain (`blog`, `www`, or `store`, for example) as the record **Name**. +Then, you would create a corresponding [IP address resolution record](/dns/manage-dns-records/reference/dns-record-types/#ip-address-resolution) (`A`, `AAAA`, or `CNAME`), specifying the label for your subdomain (`blog`, `www`, or `store`, for example) as the record **Name**. diff --git a/src/content/partials/dns/dns-scan-procedure.mdx b/src/content/partials/dns/dns-scan-procedure.mdx index c43e87c334388e..8137e53734f35d 100644 --- a/src/content/partials/dns/dns-scan-procedure.mdx +++ b/src/content/partials/dns/dns-scan-procedure.mdx @@ -24,7 +24,7 @@ Since the quick scan is not guaranteed to find all existing DNS records, you nee
Most subdomains serve a specific purpose within the overall context of your website. For example, `blog.example.com` might be your blog, `support.example.com` could be your customer help portal, and `store.example.com` would be your e-commerce site. - Even if you do not require specific subdomains, you might want to set up at least the `www` subdomain. It will usually point to the same content as what you have on the apex domain (`example.com`) or use a [redirect](/fundamentals/manage-domains/manage-subdomains/#redirect-a-subdomain-to-the-apex-domain). Having a DNS record on the `www` subdomain helps guarantee that a visitor who types `www.` in front of your domain address on their browser can still find your website or application. + Even if you do not require specific subdomains, you might want to set up at least a subdomain record on `www`. It will usually point to the same content as what you have on the apex domain (`example.com`) or use a [redirect](/fundamentals/manage-domains/manage-subdomains/#redirect-a-subdomain-to-the-apex-domain). Having a subdomain DNS record on `www` helps guarantee that a visitor who types `www.` in front of your domain address can still find your website or application.
* [Email records](/dns/manage-dns-records/how-to/email-records/)