What happens is that GoDaddy support (a painful story there) have their own method (using forwarding with masking)which is counter to Webflow’s method of using proxy-ssl.webflow.com (and doesn’t work anyway).
Please help. Where is the legendary Cyberdave when you need him? All I got is Webflow support person who is happy accusing GoDaddy that “their software is not working”.
Please help
Thanks much for your attention.
You are right; something is very wrong.
So I tried your suggestion, but the DNS record rejected the additional dot:
<Enter either @ or a valid host name such as: “subdomain.domain.tld”>
I want both the naked domain and the subdomain to point to (end up) at the site we see at http://charley-chicken-com.webflow.io/
without displaying the webflow address, but rather displaying my domain name.
This needs to be done by GoDaddy’s Domain Support to help you. Call them on the phone and give them the information needed from Webflow. They can actually go in your account and do this for you, no problem. With them on the phone give all this information:
Thanks, my friend. I’ve tried this 3 different times already, and they each came up with 3 (slightly) different solutions, which are all totally different from Webflow instructions (they use forwarding with masking; their own CNAME instead of Webflow’s) and none of which worked.
I’m sorry to contradict you, but apparently, they can access your account to view but not to make changes to the settings; they can however supervise as you input new settings…but they didn’t work!
I’ve seen other similar complaints on the forum here which have been resolved, so I’d rather take my chances with Webflow people …