pull down to refresh

Found the issue, for some reason I was using 1.1.1.3 which returns wrong responses but 1.1.1.1 works:
$ dig something.fromnothing.blog

; <<>> DiG 9.18.28 <<>> something.fromnothing.blog
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56616
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 17 (Filtered)
;; QUESTION SECTION:
;something.fromnothing.blog.    IN      A

;; ANSWER SECTION:
something.fromnothing.blog. 60  IN      A       0.0.0.0

;; Query time: 18 msec
;; SERVER: 1.1.1.3#53(1.1.1.3) (UDP)
;; WHEN: Tue Mar 18 11:19:22 CDT 2025
;; MSG SIZE  rcvd: 77

$ dig something.fromnothing.blog @1.1.1.1

; <<>> DiG 9.18.28 <<>> something.fromnothing.blog @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45988
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;something.fromnothing.blog.    IN      A

;; ANSWER SECTION:
something.fromnothing.blog. 1799 IN     A       188.40.28.19

;; Query time: 85 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Tue Mar 18 11:19:26 CDT 2025
;; MSG SIZE  rcvd: 71
See SERVER: 1.1.1.3#53(1.1.1.3) (UDP) in the first output.
I didn’t know about that Cloudflare service.
reply