N/A
N/A
DNS record propagation is not happening for CNAME, TXT, and MX records after configuring domain with Cloudflare.
None
DNS records
None.
Additional info: I recently configured Cloudflare for fishersmusic dog com domain. After 24 hours when checking DNS checker websites I’m finding that there has been zero DNS record propagation for CNAME, TXT, and A records. Is this normal since the domain is proxied by Cloudflare?
I should note that I have every DNS entry proxied except MX record on the advice of my e-mail provider.
Can you share a list, perhaps a screenshot, of these DNS record(s) you have issues with, so we can see how they appear in your Cloudflare Dashboard?
Here is screenshot of Cloudflare’s DNS records. They appear fine in Cloudflare. The issue is when I use dnschecker dot org for my meridianmusicschool.com domain, nothing is propagating. I’m not sure if that is normal behavior when Cloudflare being used or if something is not right.
Maybe I should ask something else: Is there a place in Cloudflare to check if DNS changes have propagated?
I’m asking, because I suspect even if the DNS checker websites show propagation they are going to show Cloudflare’s IP address since the domain is proxied and obscured.
That’s correct. All those 
hostnames resolve to Cloudflare’s proxy server IP addresses, which is expected behavior.
Those will never will change, since that’s where requests have to go before they are proxied to the origin IP address you’ve entered into DNS.
Is there a specific issue that’s caused to you start looking into your DNS settings?
Well, sort of an issue. It’s not critical, but I’ve not been able to troubleshoot it, because I can’t determine if DNS record changes are propagated around the world, or how far they’ve propagated, since the DNS checkers show red X’s for everything and I can’t find a DNS propagation checker in Cloudflare.
The issue I have three domains that are built with a technology platform called Odoo. Odoo has a website builder very similar to Wix or Squarespace. My website is hosted at Odoo, but Odoo does not handle naked domains. Therefore, when opening fishersmusic.com (no WWW) the website will not open. It is routing to fishersmusic.odoo.com, which is invalid. All other subdomains work as expected, including WWW. According to Odoo documentation this issue can be remedied with a tool like Cloudflare, so I changed my name servers to Cloudflare, but the naked domain still doesn’t resolve and since I can’t see what, if anything, has propagated I can’t really tell where the issue is failing.
Your screenshot is for meridianmusicschool.com, and you also said that’s the one with the problem.
Now you’re saying the issue is with fishersmusic.com. Let’s stick with a specific case, so we can track down what the issue may be.
Please provide a specific hostname, the Expected behavior, then the Actual behavior, and we can take a closer look for you.
At this time, that hostname is not proxied by Cloudflare, and the redirect is coming from an NGINX server hosted at Google. Cloudflare is not the cause of this issue.
> GET / HTTP/1.1
> Host: fishersmusic.com
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 302 Moved Temporarily
< Server: nginx
< Date: Sun, 09 Mar 2025 23:45:01 GMT
< Content-Type: text/html
< Content-Length: 138
< Connection: keep-alive
< Location: https://www.odoo.com/typo?domain=fishersmusic.com&autodbname=fishersmusic&hosting=am338a.odoo.com
< X-Content-Type-Options: nosniff
< Referrer-Policy: strict-origin-when-cross-origin
First, I started with Meridian domain, because we launched the new Odoo website this weekend. That said, my other two domains (fishersmusic doc com and theswitchtheatre dot com) have identical issue. All three are hosted by Odoo. All three WWW websites work as expected. All three naked domains fail to open the website and instead redirect to an invalid/non-existent subdomain of Odoo dot com. All that said, I will focus on fishersmusic.com. I had briefly pointed the name servers for fishersmusic.com back at A2 Hosting where the domain is registered. I have now switched the name servers back to Cloudflare.
What method or tool did you use to obtain the traffic information you posted showing the NGINX source?
Finally, I have no idea where that NGINX server at Google is coming from. I’m thinking that must be something Odoo is using. Regardless, this might not be a Cloudflare issue, but the question I have is if there is anything I do in Cloudflare to redirect/rewrite a naked domain to WWW.
There sure is! Because you’re having this issue with several domains, you’ve got two options:
hostname EQUALS nakeddomain.com then Static Redirect to https://www.example.comMake sure those apex hostnames are proxied through Cloudflare, and the rules will start forwarding to www.
That resolved my issue. I’ve deployed it for all three domains and the naked domain is now rewriting to WWW, respectively. Thank you for the help. Greatly appreciated.
One comment for future reference (if I need to reference this): Using curl to return call header, I’m receiving a 301 permanent move for all three naked domains. I assume that is expected response. Is there any harm to the quality of search engine results for root to return like that?
No. That is the correct way to tell a Search Engine that your site isn’t at the root.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
