2 ms·
$ dig @1.1.1.1 google.com ; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> @1.1.1.1 google.com ; (1 server found) ;; global options: +cmd ;; connection
by nathanaldensr 6y ago
$ dig @1.1.1.1 google.com
; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> @1.1.1.1 google.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
$ dig @1.0.0.1 google.com
; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> @1.0.0.1 google.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
- nurettin 6y ago$ dig @1.1.1.1 google.com ; <<>> DiG 9.11.20-RedHat-9.11.20-1.fc32 <<>> @1.1.1.1 google.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39428 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;google.com. IN A ;; ANSWER SECTION: google.com. 249 IN A 216.58.206.174 ;; Query time: 9 msec ;; SERVER: 1.1.1.1#53(1.1.1.1) ;; WHEN: Sat Jul 18 00:38:35 +03 2020 ;; MSG SIZE rcvd: 65
- ed25519FUUU 6y agoBoth the primary and the secondary going down is a killer. It's enough to make me switch out the secondary to a non-cloudflare DNS. Even when the secondary works the performance is pretty miserable. Adds about a 1s latency to each DNS resolution while it wait's for the primary to fail.
- nathanaldensr 6y agoYep. I quickly logged into my home Pi-hole and unchecked both IPv4 Cloudflare DNS servers.