Issues with 1.1.1.1 service?

Website, Application, Performance DNS & Network
1

Anyone else having issues with 1.1.1.1 not responding to some DNS queries? More info here: https://www.reddit.com/r/CloudFlare/comments/10ssqq0/anyone_else_having_issues_with_cloudflare_dns/j73oaua/

2

I’m going to re-post the info in that reddit comment so it’s more easily accessible.

[In reply to “Anyone else having issues with Cloudflare DNS today?”]

Yes, I am. I’ve been investigating. I am getting different responses back depending of the location of the query. For example, if I try to query 1.1.1.1 for duckduckgo.com from my AWS-hosted linux instance, I get back this:

~$ dig duckduckgo.com @1.1.1.1

; <<>> DiG 9.11.3-1ubuntu1.18-Ubuntu <<>> duckduckgo.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11280
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;duckduckgo.com.                        IN      A

;; ANSWER SECTION:
duckduckgo.com.         130     IN      A       52.149.246.39

;; Query time: 1 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Feb 03 14:57:49 CST 2023
;; MSG SIZE  rcvd: 59

But if I try it from my home internet connection, here is what I get:

~$ dig duckduckgo.com @1.1.1.1

; <<>> DiG 9.16.1-Ubuntu <<>> duckduckgo.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 1412
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; OPT=15: 00 16 ("..")
;; QUESTION SECTION:
;duckduckgo.com.                        IN      A

;; Query time: 70 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Feb 03 14:53:25 CST 2023
;; MSG SIZE  rcvd: 49

Traceroute for the first dig (works):

~$ traceroute -n 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
 1  * * 216.182.238.193  4.125 ms
 2  100.66.8.216  4.633 ms 100.65.57.144  2.259 ms 100.66.32.46  2.248 ms
 3  240.0.60.84  1.056 ms 240.0.232.126  1.042 ms 100.66.28.22  6.939 ms
 4  240.0.232.19  1.023 ms  1.008 ms 240.0.60.25  0.991 ms
 5  241.0.5.14  0.968 ms 240.0.44.12  0.967 ms 240.0.44.19  0.954 ms
 6  240.0.28.18  0.941 ms 240.0.44.27  0.248 ms 240.0.28.24  0.891 ms
 7  240.0.44.20  0.864 ms 240.0.44.16  0.845 ms 240.0.44.19  0.820 ms
 8  52.93.29.5  1.649 ms 242.0.147.33  1.038 ms 100.66.52.120  5.038 ms
 9  52.93.28.209  0.775 ms 100.100.34.40  0.734 ms 100.100.34.88  0.715 ms
10  100.100.34.46  0.704 ms 99.83.90.167  1.925 ms 100.100.34.46  0.590 ms
11  172.70.132.2  1.529 ms 240.0.28.26  0.527 ms 99.83.90.167  1.176 ms
12  172.71.220.3  9.631 ms 240.0.44.30  0.508 ms 172.70.132.2  0.872 ms
13  1.1.1.1  0.755 ms 242.0.147.33  1.370 ms 1.1.1.1  0.600 ms

Traceroute for the second dig (doesn’t work)

~$ traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max
  1   172.27.208.1  0.253ms  0.123ms  0.127ms
  2   10.12.13.1  22.161ms  2.858ms  1.349ms
  3   96.120.48.65  9.829ms  12.919ms  10.307ms
  4   68.85.168.77  17.819ms  10.823ms  33.635ms
  5   68.87.175.161  12.181ms  12.053ms  10.919ms
  6   162.151.138.49  10.720ms  12.546ms  11.572ms
  7   68.86.232.98  42.691ms  11.412ms  10.755ms
  8   69.241.114.158  15.714ms  12.136ms  43.270ms
  9   1.1.1.1  12.021ms  12.218ms  16.960ms

Going to keep investigating here. But this is annoying.

EDIT: also the failure here is somewhat intermittent. I’d say about 1 out of every 10 queries returns a valid response; the rest either fail immediately, or after a timeout occurs.

3

This appears to be resolved, at least for me. I can no longer repro.

4

Glad to hear the issue is resolved.

5