How to Resolve DNS Propagation Issues After Updating Records

[modern crown]

I recently transferred the DNS for two domains from a registrar. I deleted one A record and converted another to a CNAME record. Unfortunately, the changes are not propagating globally, and A records still appear when I query against 1.1.1.1. I also cleared the cache via https://one.one.one.one/purge-cache/ and set the domain to developer mode.

Any ideas on how to fix this?

[onyx oak]

What's the domain/the records you should be seeing but aren't?

set the domain to developer mode.
dev mode is just no http cache, there's no extra dns cache Cloudflare does by itself (excluding resolver/local dns cache of course)

[modern crown]

It is cengiz.ilerler.info and right now it is in developer mode, and these are the entries https://app.screencast.com/TZ4TLrNYiJN8D

[onyx oak]

those are all proxied so -- so you'll see Cloudflare's A/AAAA records to their Reverse Proxy and then the CNAMEs will be resolved internally

[dim sierra]

DNS over Discord: A records

cengiz.ilerler.info A @1.1.1.1 +noall +answer

NAME                | TTL  | DATA          
--------------------+------+---------------
cengiz.ilerler.info | 300s | 104.21.15.218 
cengiz.ilerler.info | 300s | 172.67.164.131

diggy diggy hole · Jul 28, 2024, 7:15 PM

[modern crown]

ok but the external service is asking for https://app.screencast.com/ghRDMQadboum0
any idea how can I make it work?

[onyx oak]

unproxy the record/dns-only

ps. You've got a redirect loop on that because your SSL/TLS Encryption setting is "Flexible", even if you don't plan on using proxy for that subdomain changing it to Full (Strict) would avoid issues in the future/with other proxied records. Under SSL/TLS -> Overview in the Cloudflare dashboard for your domain, go to "Full (Strict)"