New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Cloudflare Public DNS Resolver service may be down
Cloudflare Public DNS Resolver(1.1.1.1) sometime returns SERVFAIL error.
; <<>> DiG 9.18.12-0ubuntu0.22.04.3-Ubuntu <<>> google.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 28423
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 10 (RRSIGs Missing): (failed to verify DS com.)
;; QUESTION SECTION:
;google.com. IN A
;; Query time: 15 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Wed Oct 04 17:55:42 JST 2023
;; MSG SIZE rcvd: 69
Comments
Check again
Had the same issue today
Apparently https://www.cloudflarestatus.com/incidents/j3h00yhjyw6p
Its always a batter idea to use both Cloudflare and Google DNS together.
Public DNS is meant to be distributed
No reason to rely soley on 1.1.1.1 if you need 100 % avaliability
I often pair Cloudflare with Quad9
I think the best idea is to have local caching recursor. If latency matters, just use it as forwarder to Cloudflare, Google, Quad9 etc and cache the responses.