The community member is trying to run a web application on a subdomain, but is having issues with the TXT record verification. They have set up a CNAME record in Cloudflare, but the TXT record is not being recognized by the web application. The community member has double-checked the settings, but the issue only occurs on subdomains, not on root domains.
The comments suggest that the issue may be due to DNS propagation, and that the community member should wait for the changes to take effect. Another comment mentions that there may be a priority for already established DNS records to be rechecked. One comment also notes that the community member is getting a "CNAME Cross-User Banned" error, which is likely due to a Cloudflare security policy.
The solution was found by the community member, who realized that they had missed a letter in their own domain name when setting it up in the web application, which was the cause of the issue.
I want to run WS on a subdomain. I have hub.####.com created as a CNAME in Cloudflare and the value of that record set to the value WS provides. TTL is 1 min. Proxy is disabled.
Where I run into a problem is with the TXT record. I put the values provided by WS into CloudFlare but all I get from the WS side when I do a "check status" is an error that says:
Status: Failed to verify
TXT Record "_webstudio_is.hub.####.com" not found
The record exists in CloudFlare. TTL is set to 1 min.
I've double and tripled check all of the names and values but cannot figure out why it keeps failing. I only have this issue on subdomains. I've got several root domains set up with WS and CloudFlare that work perfectly.
Is there something I'm missing? DNS has always been my kryptonite so quite likely it's something simple.
Not sure. If I go to the URL, it kicks back some CNAME Cross-User Banned error. The host is configured as a CNAME across accounts on Cloudflare, which is not allowed by Cloudflare's security policy.
I'll just launch my root domain WS site over there in the meantime 🙂 Converting all of my WordPress and Static sites over because WS is the most magical thing since the creation of the internet (IMHO).
Found the solution. It's pretty simple. "Don't be a moron." lol I missed the letter "t" in my own domain name when setting it up in WS. Classic PEBKAC error.
