CF DNS server returns wrong IP address

Hi Colleagues!

I have created few days ago A-type DNS record sun.chertkov.info with IP 141.147.66.66 and DNS only Proxy status.
But I see the wrong DNS resolution even from CF DNS servers:


$ dig sun.chertkov.info @delilah.ns.cloudflare.com

; <<>> DiG  <<>> sun.chertkov.info @delilah.ns.cloudflare.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27739
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;sun.chertkov.info. IN A

;; ANSWER SECTION:
sun.chertkov.info. 60 IN A 172.67.179.11
sun.chertkov.info. 60 IN A 104.21.51.106

;; Query time: 212 msec
;; SERVER: 162.159.38.99#53(delilah.ns.cloudflare.com) (UDP)

AAAA record also returns wrong response:

$ dig AAAA sun.chertkov.info @delilah.ns.cloudflare.com

; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> AAAA sun.chertkov.info @delilah.ns.cloudflare.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43048
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;sun.chertkov.info.		IN	AAAA

;; ANSWER SECTION:
sun.chertkov.info.	60	IN	AAAA	2606:4700:3030::ac43:b30b
sun.chertkov.info.	60	IN	AAAA	2606:4700:3037::6815:336a

;; Query time: 60 msec
;; SERVER: 162.159.38.99#53(delilah.ns.cloudflare.com) (UDP)

Also I have the root A and AAAA types DNS records with the same IPs, but with Proxied mode.
I can’t fix the issue. Can you help me fix it please?
Thanks in advance!

Regards,
Denis

I fixed the issue.
Problem was:
I had 2 same DNS records: A and AAAA types. If I set Proxy mode for the AAAA record, A record automatically set to Proxy too, but in the UI I still see the DNS only Proxy mode.
When I disabled Proxied mode for both A and AAAA records, it works perfectly.

Looks like a CF bug.
How can I report about the bug to the CF?

Regards,
Denis

That is not a bug.

4 Likes

Thanks a lot!
I was just inattentive.

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