Www cname record is not prpogated if I set proxy status as Proxied

I’ve added a single cname record for www pointing to my app hosted on pythonanywhere ,
if I set proxy status “Off” my site is reachable and if I check through any DNS checker I see my record is propagated , but when I set it to “Proxied” my site isn’t reachable nor the record is shown on any DNS checker …
I have waited for 48 hrs and it’s still the same …
I.ve looked around the communitie and found some people are checking using dig , not familiar with this tool but I’ve provided it for refrence …

C:\Users\Azzam>dig www.laft.sa

; <<>> DiG 9.16.44 <<>> www.laft.sa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61000
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;www.laft.sa. IN A

;; ANSWER SECTION:
www.laft.sa. 299 IN A 104.21.11.64
www.laft.sa. 299 IN A 172.67.165.81

;; Query time: 599 msec
;; SERVER: 172.17.2.1#53(172.17.2.1)
;; WHEN: Thu Oct 05 14:47:52 Arab Standard Time 2023
;; MSG SIZE rcvd: 72

What error do you receive?

This site can’t be reached

You can check at

https://www.laft.sa

And here is Dns checker cname result :


https://dnschecker.org/#CNAME/www.laft.sa

This site can’t be reached

You can check at

https://www.laft.sa

And here is Dns checker cname result :

https://dnschecker.org/#CNAME/www.laft.sa

ERR_TOO_MANY_REDIRECTS is a pretty common error when SSL isn’t configgured correctly. Check the linked article to the error message itself.

The CNAME record doesn’t appear, because when proxied, the origin is obfuscated in order to direct ther traffic to Cloudflare. That’s expected. As dig indicated it resolves to an IP address.

1 Like

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.