Skip to content

Commit f1c1d5d

Browse files
authored
[DNS] Update cname-domain-verification.mdx
1 parent a40b924 commit f1c1d5d

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

src/content/docs/dns/manage-dns-records/troubleshooting/cname-domain-verification.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,15 @@ You may find issues if you have one of the following:
2020
* The CNAME record you created for domain verification is set to [**Proxied**](/dns/proxy-status/).
2121
* The CNAME record is correctly set to DNS only (not proxied) but, in your [zone settings](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings), [**CNAME flattening for all CNAME records**](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records) is enabled.
2222
* The CNAME record is correctly set to DNS only (not proxied) but CNAME flattening is [enabled for that record specifically](/dns/cname-flattening/set-up-cname-flattening/#per-record).
23+
* A [NS record](https://www.cloudflare.com/learning/dns/dns-records/dns-ns-record/) exists for the subdomain
2324

2425
## Solution
2526

2627
Make sure that:
2728

2829
* In your zone DNS settings: [**CNAME flattening for all CNAME records**](/dns/cname-flattening/) is disabled.
2930
* On the DNS records table: you have filled in the CNAME record fields correctly, proxy status is set to **DNS only**, and **Flatten** is disabled.
31+
* Review the NS configuration, and either:
32+
* make sure that your record is configured as expected with the service provider that the NS record points towards
33+
* remove the NS record so that the DNS resolution this record is resolved to the target you've configured on Cloudflare. (but be careful as this may affect other records!)
3034

0 commit comments

Comments
 (0)