Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion src/content/docs/dns/proxy-status/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -95,4 +95,13 @@ When an A, AAAA, or CNAME record is **DNS-only** — also known as being gray-cl

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.

<Render file="mix-proxied-and-unproxied" product="dns" />
<Render file="mix-proxied-and-unproxied" product="dns" />

## Verification records

Service providers might require to create a DNS verification record, usually a TXT or CNAME record.
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.
As proxied records will return Cloudflare IPs, verification CNAME needs to be set to DNS-only.

[CNAME flattening](/dns/cname-flattening/) also may interfere in the verification process: it is recommended to disable CNAME flattening if you need to set up verification CNAME records.

Loading