Can't get cloudflare domain to work with google site

[rachelbulkley]

What is the name of the domain?

covenantofgraceasheville[dot]com

What is the error message?

This site can’t be reached Check if there is a typo in covenantofgraceasheville.com. If spelling is correct, try running Windows Network Diagnostics. DNS_PROBE_FINISHED_NXDOMAIN

What is the issue you’re encountering

I followed the directions to connect the custom domain by creating a CNAME record

What steps have you taken to resolve the issue?

I’ve deleted and re-followed the steps multiple times, I’ve watched youtube videos and read the forum content

What feature, service or problem is this related to?

I don’t know

What are the steps to reproduce the issue?

attempt to visit the site at the domain

Screenshot of the error

[cscharff]

What value did you use for the CNAME record you created?

[rachelbulkley]

Hi cscharff! I’m attaching a screenshot to show you

[cscharff]

The first screenshot is not visiting the www record, just the root domain covenantofgraceasheville.com. for which a record does not exist.

When visiting www.covenantofgraceasheville.com there is a too many redirects error which most of the time can be resolved by setting your SSL to Full (Strict).

For the root domain to redirect to www (assuming that’s your intent) add an AAAA record with a value of 100:: and set it to proxied. Then follow these instructions to redirect the root domain to www.

Redirect from root to WWW · Cloudflare Rules docs

[rachelbulkley]

Hi again. I changed the ssl to Full. I’m so lost though on the AAAA record and if thats even what I want/need. when i type in www.covenantofgraceasheville.com it automatically shows as the root covenantofgraceasheville.com in the url bar. This feels weirdly impossible and I just want to cry.

[rachelbulkley]

[cscharff]

The web browser vendors decided that it was better to shorten the URL when typed in and hide the www. I think it was a horrid choice, but that’s a UI artifact (if you highlighted it and chose to copy / paste it into a word doc you’d see the www).

The AAAA record is/was because Google’s site isn’t configured to accept requests for the root domain, just the www website, so the other part of my answer was to set up an automatic redirect to send requests for the root domain to the www.

Try changing just the www record to (DNS Only) because it may be the site need to authorize / authenticate with Google before it can be deployed. I don’t use Google’s tools but it’s a reasonable guess I think.