DNS records not updated even when disabling proxy

I have changed my DNS over 2 hours ago and they still havent updated. I have even tried to disable the cloudflare proxy and then pinged the domain and it still points out to my old server IP. I dont understand why the enabling/disabling CL proxy is almost instant but updating the target takes more than 2 hours to propagate in CL databases ?

2 Likes

Seems like cloudflare DNS servers are stuck right now, even after changing my DNS servers to 1.1.1.1 it still pings the OLD server’s IP.

1 Like

i’ve notice the same. adding new CF proxy A’s are instenet, but anything that does not proxy, not reflecting/propagating.

There may be a new issue with DNS. Open a ticket and then post the ticket # here so we can escalate.

I’ve just tried to replicate this and my DNS changes are propagating almost instantly whether they’re :orange: or :grey:.

Changing the IP that a :grey: record points to was reflected in under a minute for me.

if you look at my thred, you can see some more technical info.

  1. adding a new A works fine for proxy
  2. removing A, don’t work, CF will still resolve it.
  3. adding new TXT never show
  4. Adding a new IP to a proxyed A, dont update. still goes to old IP

testing with 3 domains.

I can confirm that there is a problem at least for some of domains too. I tried adding new subdomains, changing proxied subdomains, etc. but only one of the changes is applied. I’m on free tier and does not have access to ticketing system.

Cannot confirm this. Stopped resolving seconds after I removed it.

Also can’t confirm this, newly added TXT showed up in seconds for me.

Not sure what you mean specifically by this, but I’ve tried both :orange: and :grey: records and they are all resolving and changing when I update the IP.

I set a TXT record and shows fine on the dns editor but does not show up on the internet.

then i use another domain and created an “A” with CF proxy, works fine.
disabled CF proxy and then deleted the “A” but DNS still resolve the DNS A to CF proxy.

TTL shows at 65

2 Likes

Same issue, posted about it in a different thread. ‘A’ record not updating. Dnschecker.org shows the old IP still.

1 Like

I was having a similar issue for about an hour, but now my DNS changes and new domains resolve correctly. Probably waiting a little longer will fix it for you too.

1 Like

for testing

test.apogee.lk - this was deleted like 20min back.

dig test.apogee.lk @1.1.1.1

; <<>> DiG 9.16.21 <<>> test.apogee.lk @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6180
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;test.apogee.lk. IN A

;; ANSWER SECTION:
test.apogee.lk. 299 IN A 172.67.184.218
test.apogee.lk. 299 IN A 104.21.72.129

;; Query time: 126 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sun Nov 07 02:57:30 +0530 2021
;; MSG SIZE rcvd: 75

That’s not a TXT record, but that record is there

DNS Checker - DNS Check Propagation Tool

And loads just fine, if you ignore the 403s

sitemeer.com/#test.apogee.lk

exactly my point, it was DELETED like 20 min back. but CF still resolve it, TTL is 270 (270 seconds.)

read the OP

below A was removed close to 45min back

dig test.apogee.lk @1.1.1.1

; <<>> DiG 9.16.21 <<>> test.apogee.lk @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52964
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;test.apogee.lk. IN A

;; ANSWER SECTION:
test.apogee.lk. 96 IN A 104.21.72.129
test.apogee.lk. 96 IN A 172.67.184.218

;; Query time: 123 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sun Nov 07 03:27:09 +0530 2021
;; MSG SIZE rcvd: 75

below TXT was added 1 hour ago

[[email protected] ~]$ dig _acme-challenge.apogee.users.orbitsl.net txt @1.1.1.1

; <<>> DiG 9.16.21 <<>> _acme-challenge.apogee.users.orbitsl.net txt @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55456
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;_acme-challenge.apogee.users.orbitsl.net. IN TXT

;; AUTHORITY SECTION:
orbitsl.net. 3236 IN SOA dina.ns.cloudflare.com. dns.cloudflare.com. 2261696913 10000 2400 604800 3600

;; Query time: 133 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sun Nov 07 03:27:51 +0530 2021
;; MSG SIZE rcvd: 131

Okay, I seem to be seeing some issues with free zones similar to how you’re describing. Looking further…

3 Likes

I’ve merged these two threads, as they’ve pretty much become one conversation.

2 Likes

I do seem to be able to confirm an issue with DNS updates only on Free zones. I’m escalating this through as a priority.

5 Likes

This has gone through as the highest priority we can, I’ll post any updates I receive on this thread.

5 Likes

I’m having the same or similar issue. I changed a proxied ‘A’ record’s IP address and it is not propagating. dnschecker.org still shows the old IP. Any help on this would be appreciated.