So here is the problem. Hover just doesn’t handle forwards sensibly. Who have you had better experience with.
a-view.org (WITHOUT https://) resolves to https://test-view.onrender.com. hover says there is NO WAY to forward from https://a-view.org because there is no cert associated with a-view.org. I suppose that is true. But, I didn’t have that problem with Digital Ocean hosting a ghost site and the DNS records with Hover as the registrar.
Hover cannot support cname @ to test-aview.onrender.com.
The other problem with the hover approach (a records to themselves, with a forward to test-view.onrender.com) is that users have to delete https:// when they type in a-view.org. Every modern browser tries to enforce https for secure browsing so users have to manually delete the https://–which they never do for anything else. So, this is a non-starter.
the second problem is that as users click around the site, the urls they see are:
https://test-aview.onrender.com/ and not https://a-view.org/. Users should never see test-aview.onrender.com. that is the whole point of custom domains.
So, tell me that this works correctly with cloudflare or cheapnames. I am happy to kiss hover goodby. they may be well priced and basically ethical, but apparently technically limited. The support person actually recommended cloudflare. But, what she meant was keep the domain name at Hover, so they got the renew fee for doing nothing, and host the DNS records at cloudflare (which was basically what I was doing with Digital Ocean and Hawkhost (for some older wordpress blogs)).
I want to move the whole shebang to another provider. There is no reason to keep paying hover for being a technically limited registrar.
How can I verify if this will work correctly at cloudflare or namecheap or anyone else.
Sorry this is long. I thought this would be trivial but nothing is trivial.