Cloudflare CNAME not resolving is no longer an issue with a little assistance from our experts. 

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Services.

Let’s take a look at how our Support Team is ready to help customers when Cloudflare CNAME is not resolving.

Cloudflare CNAME not resolving

If you are having trouble with CNAME, you are in the right place. Cloudflare relies on a setup where it uses its own IPs to proxy the address that we are using. In other words, Cloudflare replaces our IP with one of its own. Furthermore, we can set up CNAME records within Cloudflare by bypassing their server. This causes the domain to appear as an A record.

If our Cloudflare CNAME is not resolving, our Support Techs recommend checking to ensure the CNAME record is added correctly in the DNS settings in the domain registrar.

Furthermore, we can verify the CNAME record via a third-party tool as seen below:

1. First, head to this link.
2. Then, enter our custom domain URL in the Domain Name field.
3. Next, choose CNAME from the drop-down list.
4. Finally, click Search.

The results of the above steps will help us know if the CNAME is propagated across servers all over the globe. Green ticks in the right side column indicate success.

According to our Support Team, the root domain’s “A” record is an IP address. Moreover, “www” is a CNAME to the site at WPEngine. Additionally, this resolves to the IP address same as the A record.

Once they resolve, we can click the symbol seen below to proxy them.

Additionally, when we click this image next to a root CNAME, it flattens to appear as an A record.

In some scenarios, the root domains may stop working as the CNAME setup insists on using ‘www’ for our domain. In that case, we have to redirect requests to the root domain rather that the ‘www’ subdomain.

[Need assistance with a different issue? We are available 24/7.]

Conclusion

In brief, our skilled Support Engineers at Bobcares demonstrated what to do when Cloudflare CNAME is not resolving. The process involves checking to ensure the CNAME record is added correctly in the DNS settings in the domain registrar.