Edge discovery: error looking up Cloudflare edge IPs: the DNS query failed

What is the name of the domain?

photos.stegosaurusdormant.com

What is the error number?

N/A

What is the error message?

edge discovery: error looking up Cloudflare edge IPs: the DNS query failed error=“lookup _v2-origintunneld._tcp.argotunnel.com on 127.0.0.11:53: read udp 127.0.0.1:58132->127.0.0.11:53: i/o timeout”

What is the issue you’re encountering

I’m running a service in a docker container on my homelab machine and exposing it to the WAN using a Cloudflare tunnel. Everything was working great up until last night, but now the service cannot be reached via the Cloudflare tunnel. The cloudflared Docker container’s logs show the above error message. The service is still reachable from my local network.

What steps have you taken to resolve the issue?

  1. verify that the service is up (I can reach it from my local network)
  2. check the cloudflared docker container logs (that’s where I see the above error message)
  3. verify that my homelab machine can resolve the DNS query that’s failing:
dig srv _v2-origintunneld._tcp.argotunnel.com

; <<>> DiG 9.18.24-1-Debian <<>> srv _v2-origintunneld._tcp.argotunnel.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42443
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;_v2-origintunneld._tcp.argotunnel.com. IN SRV

;; ANSWER SECTION:
_v2-origintunneld._tcp.argotunnel.com. 219 IN SRV 2 1 7844 region2.v2.argotunnel.com.
_v2-origintunneld._tcp.argotunnel.com. 219 IN SRV 1 1 7844 region1.v2.argotunnel.com.

;; Query time: 4 msec
;; SERVER: 192.168.0.174#53(192.168.0.174) (UDP)
;; WHEN: Wed Jan 15 10:07:44 EST 2025
;; MSG SIZE  rcvd: 156
dig region2.v2.argotunnel.com

; <<>> DiG 9.18.24-1-Debian <<>> region2.v2.argotunnel.com.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19225
;; flags: qr rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
region2.v2.argotunnel.com. 65872 IN	A	198.41.200.233
region2.v2.argotunnel.com. 65872 IN	A	198.41.200.113
region2.v2.argotunnel.com. 65872 IN	A	198.41.200.43
region2.v2.argotunnel.com. 65872 IN	A	198.41.200.53
region2.v2.argotunnel.com. 65872 IN	A	198.41.200.23
region2.v2.argotunnel.com. 65872 IN	A	198.41.200.63
region2.v2.argotunnel.com. 65872 IN	A	198.41.200.193
region2.v2.argotunnel.com. 65872 IN	A	198.41.200.13
region2.v2.argotunnel.com. 65872 IN	A	198.41.200.73
region2.v2.argotunnel.com. 65872 IN	A	198.41.200.33

;; Query time: 48 msec
;; SERVER: 192.168.0.174#53(192.168.0.174) (UDP)
;; WHEN: Wed Jan 15 10:08:39 EST 2025
;; MSG SIZE  rcvd: 214
  1. verify that my homelab machine can reach at least one of those IP addresses:
ping 198.41.200.233
PING 198.41.200.233 (198.41.200.233) 56(84) bytes of data.
64 bytes from 198.41.200.233: icmp_seq=1 ttl=54 time=20.0 ms
64 bytes from 198.41.200.233: icmp_seq=2 ttl=54 time=18.8 ms
64 bytes from 198.41.200.233: icmp_seq=3 ttl=54 time=20.5 ms
64 bytes from 198.41.200.233: icmp_seq=4 ttl=54 time=18.9 ms
^C
--- 198.41.200.233 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 18.824/19.550/20.495/0.717 ms

What are the steps to reproduce the issue?

Visit https://photos.stegosaurusdormant.com/ and you’ll see that the Cloudflare tunnel is down