Skip to content

Commit 09f46ad

Browse files
authored
[DNS] Update index.mdx
Following case 01688018
1 parent fe139da commit 09f46ad

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

src/content/docs/dns/proxy-status/index.mdx

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,4 +95,10 @@ When an A, AAAA, or CNAME record is **DNS-only** — also known as being gray-cl
9595

9696
In addition to potentially exposing your origin IP addresses to bad actors and [DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/), leaving your records as **DNS-only** means that Cloudflare cannot [optimize, cache, and protect](/fundamentals/concepts/how-cloudflare-works/) requests to your application or provide analytics on those requests.
9797

98-
<Render file="mix-proxied-and-unproxied" product="dns" />
98+
<Render file="mix-proxied-and-unproxied" product="dns" />
99+
100+
## Verification records
101+
102+
Service providers might require to create a DNS verification record, usually a TXT or CNAME record.
103+
In the case of a CNAME record, it needs to be set to DNS-only on the Cloudflare Dashboard: your service provider needs to be able to resolve this record to the value they've asked you to configure.
104+
As proxied records will return Cloudflare IPs, verification CNAME needs to be set to DNS-only.

0 commit comments

Comments
 (0)