The hush cname ends up being hush.hush.it.com when I hover my mouse over it, could that be the issue?
What am I doing wrong? DNS by Cloudflare.
Here is my site Read-Only: [LINK][1]
([how to share your site Read-Only link][2])
[1]:
[2]: Share your site and invite collaborators - Webflow University Documentation
You should only need the CNAME record for the hush subdomain. Try removing the two A records and the www CNAME record.
I’ll give that shot. But I feel like the issue is due to my domain being hush.it.com when I add the cname record according to the Webflow suggestions as hush, it resolves to hush.hush.it.com
You’re effectively using a registrar that resells names under the IT.COM domain. Most the DNS zone you’re configuring is HUSH.IT.COM, so you’d likely treat it as a regular domain name config rather than a subdomain config.
It’s a bit weird, but I think you’d keep the A records and the www and ditch the hush CNAME, and everything should logically work in the context of HUSH.IT.COM.
If you’re trying to make hush.it.com work rather than www.hush.it.com, you probably need CNAME flattening support. This is all a bit nonstandard, so problems wouldn’t be surprising.
If you still seeing weirdness I’d hit support, they’ve likely seen this before and will have a strategy for dealing with it.
No luck so far, still showing me the same warning telling me to add the cname record and domain still isn’t connected to webflow site.
Ah ok, only reason I mentioned that is because when I tried using the auto connect feature, I had to enter my domain as hush.it.com. Otherwise the text field would default it to it.com. I’ll try that, but then wouldn’t the cname error persist?
I never use quickconnect, I prefer to see the configuration directly. It likely thinks you’re trying to configure a subdomain of a domain you own, which is not the case. You do not have access to the it.com DNS zone, only to the hush.it.com DNS zone.
That’s why your hush CNAME is coming up as hush.hush.it.com.
You are sandboxed into your subdomain’s DNS zone, and all of your entries are relative to that zone.
As I said it’s a weird setup. Use regular manual connect and handle it like a regular domain name, I think you’ll get the config you need-
Again, it will likely be www.hush.it.com that you end up with.
Also remember that DNS propagation takes 24-48 hours, so updates may take awhile.
Yea, quick connect wasn’t working so I manually added it and I’m getting that error. I opened a support ticket and they told me to delete both A records and the www record and only keep the hush record. So I’ve done that and now I guess we play the waiting game to see if it worked.
Yep, I would be surprised if that works here since it.com has set up things a bit differently.
So far still seeing hush.hush but fingers crossed.
I feel like by that logic, if I change the cname record from hush to @ it should work, but then I wouldn’t be able to assign any A addresses to root. Would it be possible to add the 2 Webflow A entries under the www name?
You cannot add an @ CNAME unless it.com happens to support flattened CNAMES, which is unlikely.
That’s why I think you’re stuck with www.hush.it.com.
But try it all, see what happens.
This should mean that my dns is all configured correctly and the issue is on webflow side thinking my Domain is hush.hush.it.com instead of hush.it.com right?
This is looking pretty functional, now on the Webflow side, you’d try to add www.hush.it.com manually as a domain and set it as the default domain.
If that’s accepted, it should be able to provision SSL properly.
Make sure to republish your site once it’s added.
That’s the entry Webflow told me to add, I have an odd feeling that this is trying to resolve to www.hush.hush.it.com…
Exactly, I’m quite sure that won’t work. Again, you appear to be sandboxed into your subdomain’s DNS zone, so anything you add there is on top of hush.it.com.
This whole thing is weird and it.com is definitely not listed as a TLD or ccTLD. But strangely it also has resellers like GoDaddy.
I’d probably punt and buy hush-it.com or something much more technically legit that you have full domain name authority and DNS control over.
Thanks for all your help! It was super informative and I managed to learn a fair bit. So it seems that Webflow seems to think www.hush would resolve as www.hush.it.com if I put that in the cname in my DNS. But I managed to get around it by putting www instead of www.hush.
Nice! I’m happy that my wild theory was correct, such a weird setup. The site looks good! And I’m glad that Webflow was able to provision the SSL, I was concerned about that since it.com has such an unusual config.
Thank you! The biggest blockade is that I can’t have root set as a cname if I already have 2 A records using root. What if I swapped it around and set www for the A records and used root for the cname?
Lookup the CNAME flattening I mentioned above, What you’re needing is an @ CNAME record, which most DNS’s do not support. Check with it.com, you might get lucky.
Normally when I need that, I’d use Cloudflare’s DNS, however in your case I don’t think that’s possible since you do not own it.com.
