Skip to content

Commit ae8b809

Browse files
[Chore] Fix links and broken anchor and update Style Guide (#18381)
* Remove broken anchor * Clean up /inline-errata/ from EDNS RFC links * Update Style Guide with note about not using inline-errata RFC
1 parent 42ae022 commit ae8b809

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

src/content/docs/dns/dns-firewall/faq.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Yes. `SERVFAIL` is treated like any other negative answer for caching purposes.
3232

3333
<Details header="Does DNS Firewall support EDNS Client Subnet (ECS)?">
3434

35-
Yes. Often, DNS providers want to see a client's IP via <GlossaryTooltip term="EDNS Client Subnet (ECS)">EDNS Client Subnet (ECS)</GlossaryTooltip> ([RFC 7871](https://www.rfc-editor.org/rfc/inline-errata/rfc7871.html)) because they serve geographically specific DNS answers based on the client's IP. With EDNS Client Subnet enabled, the DNS Firewall will forward the client's IP subnet along with the DNS query to the upstream nameserver.
35+
Yes. Often, DNS providers want to see a client's IP via <GlossaryTooltip term="EDNS Client Subnet (ECS)">EDNS Client Subnet (ECS)</GlossaryTooltip> ([RFC 7871](https://www.rfc-editor.org/rfc/rfc7871.html)) because they serve geographically specific DNS answers based on the client's IP. With EDNS Client Subnet enabled, the DNS Firewall will forward the client's IP subnet along with the DNS query to the upstream nameserver.
3636

3737
When EDNS is enabled, the DNS Firewall gives out the geographically correct answer in cache based on the client IP subnet. To do this, the DNS Firewall segments its cache. For example:
3838

src/content/docs/dns/zone-setups/subdomain-setup/setup/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ The availability of different setups will depend on both the parent zone setup a
5050

5151
:::caution[* Subdomain zones in partial setup are not delegated]
5252

53-
Subdomains using a partial setup represent an exception in the sense that [delegation](#subdomain-delegation) does not apply in this context. As explained in the dedicated [Partial (CNAME) setup section](/dns/zone-setups/partial-setup/), this setup is intended to simply proxy individual subdomains through Cloudflare. For completeness, however, this is listed as an option in this table and the [how-to guide](/dns/zone-setups/subdomain-setup/setup/parent-on-partial/) has detailed explanation on how to achieve a subdomain zone using partial setup.
53+
Subdomains using a partial setup represent an exception in the sense that delegation does not apply in this context. As explained in the dedicated [Partial (CNAME) setup section](/dns/zone-setups/partial-setup/), this setup is intended to simply proxy individual subdomains through Cloudflare. For completeness, however, this is listed as an option in this table and the [how-to guide](/dns/zone-setups/subdomain-setup/setup/parent-on-partial/) has detailed explanation on how to achieve a subdomain zone using partial setup.
5454
:::
5555

5656
This table assumes zones that are in an [active status](/dns/zone-setups/reference/domain-status/). For example, if you need to add the parent zone to Cloudflare when its child zone already exists in a partial setup, you can [convert the parent zone to partial](/dns/zone-setups/partial-setup/setup/#1-convert-your-zone-and-review-dns-records) while it is still in pending status.

src/content/docs/style-guide/formatting/external-references.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ For general websites, consider the following recommendations about the link text
1313
* Authoritative sources for documents such as RFCs can have their own specific format for references, such as the RFC number.
1414

1515
:::note
16-
When linking to a Cloudflare blog post, sometimes we use only "blog post" for the link text.
16+
When linking to a Cloudflare blog post, sometimes we use only "blog post" for the link text.
1717
:::
1818

1919
## Referencing RFCs
@@ -37,8 +37,8 @@ When linking to an RFC (or RFC section), consider using a link to the following
3737
To get the link:
3838

3939
1. Go to [RFC Editor](https://www.rfc-editor.org/rfc-index.html) and search for the RFC number.
40-
2. Select HTML to open the HTML version.
41-
3. (optional) Navigate to a specific section, if necessary.
40+
2. Select **HTML** to open the HTML version. If available, do **not** use **HTML with inline errata** as this version should not be used as reference.
41+
3. (Optional) Go to a specific section, if necessary.
4242
4. Use the current URL as the link target in Developer Documentation.
4343

4444
URL example:

src/content/glossary/dns.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ entries:
4747
general_definition: |-
4848
ECS is a DNS extension that enables recursive DNS resolvers to include client IP address information in their DNS queries.
4949
50-
Not all resolvers use ECS but, if they do, usually a part of the IP address is omitted. Sending ECS headers is generally intended to reduce latency and speed up content delivery in connection to [CDNs](/glossary/?term=cdn) and [load balancers](https://www.cloudflare.com/learning/performance/what-is-load-balancing/). The ECS mechanism is specified in [RFC 7871](https://www.rfc-editor.org/rfc/inline-errata/rfc7871.html).
50+
Not all resolvers use ECS but, if they do, usually a part of the IP address is omitted. Sending ECS headers is generally intended to reduce latency and speed up content delivery in connection to [CDNs](/glossary/?term=cdn) and [load balancers](https://www.cloudflare.com/learning/performance/what-is-load-balancing/). The ECS mechanism is specified in [RFC 7871](https://www.rfc-editor.org/rfc/rfc7871.html).
5151
associated_products:
5252
- Load Balancing
5353
- Cloudflare One

0 commit comments

Comments
 (0)