CNAME www record doesn't propagate correctly. It propagate as a A record, Why?

CNAME www record has been set, but it doesn't propagate correctly. It propagated as an A record, Why? and How can I fix it?

Erisa•10/7/24, 12:39 PM

because its proxied, cloudflare returns the proxy IPs and does the cname logic when contacting the origin server after the request hits the cloudflare cdn

Erisa•10/7/24, 12:40 PM

if you unproxy the record youll see the raw cname value but will also lose the protections and benefits of having the cloudflare proxy active

José MuñozOP•10/7/24, 12:58 PM

Hello!. Thanks for help me. This is the issue. I need to use ssl and CDN from Cloudflare, but some clients or providers tag this issue as red tag!..

Erisa•10/7/24, 1:00 PM

They're wrong, it's not an issue. It's impossible to use Cloudflare for CDN while having the CNAME resolve as a CNAME like that

Erisa•10/7/24, 1:00 PM

Every website using Cloudflare (which powers >20% of the internet) will experience the same behaviour, it's completely normal

José MuñozOP•10/7/24, 1:01 PM

Other people have experienced errors from their Brave browsers. This is part of the same issue?

Erisa•10/7/24, 1:02 PM

Which error?

José MuñozOP•10/7/24, 1:03 PM

they try to use www insted of domain and the browser does not resolve it.

Erisa•10/7/24, 1:04 PM

just having an A record and not a CNAME wouldnt cause a browser to not resolve it. have you changed dns recently? there might be dns cache on the browsers, as could there be several other reasons such as recursive dns or isps providers blocking the domain.
youre sure the error is that the browser is not resolving it? ERR_NAME_NOT_RESOLVEDERR_NAME_NOT_RESOLVED or DNS_PROBE_FINISHED_NXDOMAINDNS_PROBE_FINISHED_NXDOMAIN?

José MuñozOP•10/7/24, 1:05 PM

Erisa•10/7/24, 1:05 PM

thats not a DNS resolution error

Erisa•10/7/24, 1:06 PM

QUIC relates to HTTP/3 functionality, its odd that it errors (maybe something bad going on with their network?) but you can try turning it off:

José MuñozOP•10/7/24, 1:09 PM

ok..

José MuñozOP•10/7/24, 1:10 PM

They told me the can access using crome but usually use brave

Erisa•10/7/24, 1:10 PM

wonder if its an issue with the brave browser specifically then

Erisa•10/7/24, 1:11 PM

regardless for now id try turning off http/3 and seeing if that fixes it

José MuñozOP•10/7/24, 1:14 PM

ok.. I'm going to apply what you recommended me. I will do it tonight.. tomorrow I will show you the results.

José MuñozOP•10/7/24, 2:48 PM

They sent me another error from an app in the same domain. content.<domain>.comcontent.<domain>.com , the error is showed below

JJosé Muñoz They sent me another error from an app in the same domain. `content.<domain>.com...

Chaika•10/7/24, 3:38 PM

Your app was depending on cloudflare's ipfs? They shut that down a while ago:
https://blog.cloudflare.com/cloudflares-public-ipfs-gateways-and-supporting-interplanetary-shipyard/

All traffic using the cloudflare-ipfs.com or cf-ipfs.com hostname(s) will continue to work without interruption and be redirected to ipfs.io or dweb.link until August 14th, 2024, at which time the Cloudflare hostnames will no longer connect to IPFS and all users must switch the hostname they use to ipfs.io or dweb.link to ensure no service interruption takes place. If you are using either of the Cloudflare hostnames, please be sure to switch to one of the new ones as soon as possible ahead of the transition date to avoid any service interruptions!

would have to switch to one of the alternatives

José MuñozOP•10/7/24, 3:42 PM

yes, It depends on that..

José MuñozOP•10/7/24, 3:46 PM

They did not realize this app was out of line.. Just now..

José MuñozOP•10/7/24, 6:09 PM

Hi!.. I did this before Update Cloudflare DNS parameter and it Works!

CNAME www record doesn't propagate correctly. It propagate as a A record, Why?

Similar Threads

Similar Threads

Similar Threads