Cloudflare for Families not responding from Starlink connections

Website, Application, Performance DNS & Network
1

We have a fair number of Starlink subscribers in Saskatchewan, Canada and they have had their DNS queries fail since 9:45pm Eastern yesterday (May 5).

Queries to 1.1.1.3 and 1.0.0.3 fail like this:

root: dig @1.1.1.3 google.ca

; <<>> DiG 9.16.23 <<>> @1.1.1.3 google.ca
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

Interestingly, no problems with 1.1.1.1:

root: dig @1.1.1.1 google.ca

; <<>> DiG 9.16.23 <<>> @1.1.1.1 google.ca
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28725
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
google.ca.		22	IN	A	172.217.4.67

;; Query time: 70 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sat May 06 10:04:34 CDT 2023
;; MSG SIZE  rcvd: 54

Also noticed that mtr to 1.1.1.3 doesn’t report anything out of the ordinary:

                             My traceroute  [v0.94]
gateway1 (192.168.1.94) -> 1.1.1.3         2023-05-06T10:22:43-0500
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                       Packets               Pings
 Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 192.168.1.1                       0.0%     5    0.6   0.6   0.3   0.7   0.1
 2. 100.64.0.1                        0.0%     5   73.2  59.9  45.7  73.2  11.7
 3. 172.16.251.82                     0.0%     5   66.1  58.5  48.4  66.1   8.2
 4. 206.224.64.98                     0.0%     4   47.2  49.0  47.2  52.6   2.5
 5. 206.224.64.91                     0.0%     4   63.7  56.8  49.3  63.7   6.2
 6. 206.41.110.38                     0.0%     4   57.7  58.8  56.2  61.5   2.3
 7. 172.70.128.2                      0.0%     4   72.0  63.6  47.9  73.6  11.9
 8. 1.1.1.3                           0.0%     4   72.0  64.3  56.4  72.0   8.0

I’ve noticed this behaviour before when public resolvers apply a rate limiter.

4

The issue appears to have been resolved for all locations around 9:55pm Eastern tonight, just about an hour ago.

This kind of information I would have appreciated seeing at cloudflarestatus.com but there’s no mention of it there.

5

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