This solved the immediate problem, but I’m still not sure if I solved it properly… The original www CNAME is currently set to DNS only, and when I set it to Proxied, the website breaks…
192.0.2.1 isn’t a internet routable IP Address, it’s just used as a placeholder/for originless setups. How would that ever get to google?
If you wanted Google Sites to work, you would want to change that into a CNAME and add your apex/root domain to your Google Sites custom domains tab.
However, you’d get punished by search engines for duplicate content, so a redirect is the way to go. You can use that proxied IP like you did before, or AAAA100:: for an originless setup that just uses Cloudflare Redirects.
You could use that same redirect rule you showed before. A small modification to keep the path would be a good idea as well, if you switch Type to Dynamic, you could use concat("https://www.starhamradio.com", http.request.uri.path)
The cname is working (www.starhamradio.com), but the WWW.starhamradio.comA record is still not working. I know it has 192.0.2.1 in for the content, but my understanding is that doesn’t matter if it’s proxied…
It wouldn’t matter as long as some Cloudflare feature (Page Rules, Dynamic Redirects, etc) match it and return a response. It wouldn’t go to Google Sites, and currently it’s just timing out:
Doing a redirect using only DNS? No, why do you think you need to? You can just enable that rule again, and you can update it with the expression I gave you to so it keeps path as well.