Skip to content

Commit 883ce64

Browse files
Move detailed example to partials and add back in Fundamentals
1 parent 43d0345 commit 883ce64

File tree

5 files changed

+48
-17
lines changed

5 files changed

+48
-17
lines changed

src/content/docs/dns/manage-dns-records/proxy-status/about-proxying.mdx

Lines changed: 5 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -35,22 +35,12 @@ In addition to potentially exposing your origin IP addresses to bad actors and [
3535

3636
## Detailed explanation
3737

38-
<Example>
38+
<Render file="proxy-status-dns-table" />
3939

40-
DNS management for **example.com**:
40+
### Proxied record example
4141

42-
| Type | Name | Content | Proxy status | TTL |
43-
| :--: | :----: | :---------: | :----------: | :----: |
44-
| A | `blog` | `192.0.2.1` | Proxied | Auto |
45-
| A | `shop` | `192.0.2.2` | DNS only | Auto |
46-
</Example>
42+
<Render file="proxy-on-example" />
4743

48-
In the example DNS table above, there are two DNS records. The record with the name `blog` has the proxy on, while the record named `shop` has the proxy off (that is, **DNS only**).
44+
### DNS-only record example
4945

50-
### Proxied DNS record example
51-
52-
When a browser initiates an HTTP/HTTPS request to `blog.example.com`, a DNS resolver will convert the hostname into an IP address. Since this domain is using Cloudflare as its authoritative DNS provider, the DNS query will be routed to Cloudflare; and because the proxy is on, Cloudflare will answer with an anycast IP address. Subsequently, the browser initiates an HTTP/HTTPS request back to Cloudflare. When Cloudflare receives this request, it performs a lookup to find the matching domain and account configuration and processes the request accordingly. When needed, Cloudflare forwards the request to the configured origin server, which is `192.0.2.1`.
53-
54-
### DNS only record example
55-
56-
When the browser initiates an HTTP/HTTPS request to `shop.example.com`, a DNS resolver will convert the hostname into an IP address. Since this domain is using Cloudflare as its authoritative DNS provider, the DNS query will be routed to Cloudflare; but since the proxy is off (that is, **DNS only**), Cloudflare will answer with `192.0.2.2`. Finally, the browser initiates an HTTP/HTTPS request to the server hosted at `192.0.2.2`.
46+
<Render file="proxy-off-example" />

src/content/docs/fundamentals/concepts/how-cloudflare-works.mdx

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sidebar:
66

77
---
88

9-
import { GlossaryTooltip } from "~/components"
9+
import { GlossaryTooltip, Render } from "~/components"
1010

1111
The [Cloudflare global network](https://www.cloudflare.com/network/) can improve the security, performance, reliability, and privacy of anything connected to the Internet, such as your website, SaaS application, or corporate network.
1212

@@ -34,8 +34,19 @@ Refer to our [Load Balancing reference architecture](/reference-architecture/arc
3434

3535
In the Cloudflare dashboard, find out which DNS records are proxied by selecting your domain and navigating to the **DNS records** tab.
3636

37-
#### Protocols, ports, and methods
37+
#### Example DNS table
38+
39+
<Render file="proxy-status-dns-table" product="dns" />
40+
41+
#### Proxied record example
42+
43+
<Render file="proxy-on-example" product="dns" />
3844

45+
#### DNS-only record example
46+
47+
<Render file="proxy-off-example" product="dns" />
48+
49+
#### Protocols, ports, and methods
3950

4051
Proxying is on by default for records that serve HTTP/HTTPS traffic (A, AAAA, and CNAME records). To proxy HTTP/HTTPS traffic on [non-standard ports](/fundamentals/reference/network-ports/) or to proxy a TCP- or UDP- based application, use [Cloudflare Spectrum](/spectrum/).
4152

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
{}
3+
4+
---
5+
6+
When a browser initiates an HTTP/HTTPS request to `shop.example.com`, a DNS resolver will convert the hostname into an IP address. Since this domain is using Cloudflare as its authoritative DNS provider, the DNS query will be routed to Cloudflare; but since the proxy is off (that is, **DNS only**), Cloudflare will answer with `192.0.2.2`. Finally, the browser initiates an HTTP/HTTPS request to the server hosted at `192.0.2.2`.
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
{}
3+
4+
---
5+
6+
When a browser initiates an HTTP/HTTPS request to `blog.example.com`, a DNS resolver will convert the hostname into an IP address. Since this domain is using Cloudflare as its authoritative DNS provider, the DNS query will be routed to Cloudflare; and because the proxy is on, Cloudflare will answer with an anycast IP address. Subsequently, the browser initiates an HTTP/HTTPS request back to Cloudflare. When Cloudflare receives this request, it performs a lookup to find the matching domain and account configuration and processes the request accordingly. When needed, Cloudflare forwards the request to the configured origin server, which is `192.0.2.1`.
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
{}
3+
4+
---
5+
6+
import { Example } from "~/components";
7+
8+
<Example>
9+
10+
DNS management for **example.com**:
11+
12+
| Type | Name | Content | Proxy status | TTL |
13+
| :--: | :----: | :---------: | :----------: | :----: |
14+
| A | `blog` | `192.0.2.1` | Proxied | Auto |
15+
| A | `shop` | `192.0.2.2` | DNS only | Auto |
16+
</Example>
17+
18+
In the example DNS table above, there are two DNS records. The record with the name `blog` has the proxy on, while the record named `shop` has the proxy off (that is, **DNS only**).

0 commit comments

Comments
 (0)