I’ve got a weird one. After setting up my DNS for gettaxreliefnow.com, the primary domain is successfully published and working. However, the www subdomain shows as “Connected” but “Not published” with an error.
Webflow is telling me to “resolve issues” by creating a CNAME record, but it’s already been correctly set up in Cloudflare for hours:
CNAME Record:www → cdn.webflow.com
The main domain (A record) propagated fine, but the www subdomain seems stuck. Has anyone encountered this where one works and the other doesn’t, despite both DNS records being correct?
Specific questions:
Does the www subdomain typically take longer to propagate than the root domain?
Could this be a Cloudflare proxy (orange cloud) issue specific to CNAME records?
Is there a hidden “enable www” setting in Webflow I might have missed?
Any insights would be great! It’s frustrating when the hard part (root domain) works but the simple CNAME is causing issues.
It’s showing correctly in my DNS query from Auckland, NZ.
www.gettaxreliefnow.com. 3600 IN CNAME cdn.webflow.com.
If the Webflow dashboard is still showing issues I’d message support- I remember some others having a similar issue with the dashboard’s validation of the new items.
It could just be that your browser cache needs cleared also to clean out some old cached validation code, or that you have a browser extension interfering.
Orange cloud needs to be off. But since I’m seeing the correct value and not a proxied one, I expect you have that setup correctly.
Had this happen on a Cloudflare setup recently , turning off the orange cloud on the www CNAME fixed it instantly. Also make sure www is set as the default domain in Webflow hosting settings, otherwise it can stay stuck on “not published.”