Issue:
I am receiving an error “Couldn’t resolve SRV record” when attempting to setup cloudflared on Portainer.
More Info:
I am trying to run cloudflared as a container on Portainer but am receiving an error - I understand this is a DNS issue but cannot find the solution. The puzzling issue is that I can use dig and nslookup on my desktop but dig does not work on my server (but nslookup does). With that said, I believe my router is not an issue and I do not have a separate firewall which could be interfering.
I have four other containers currently running on Portainer which have been able to successfully deploy and update with no DNS issues.
Logs:
2023-04-23T12:31:39Z WRN Unable to lookup protocol percentage.
2023-04-23T12:31:39Z INF Initial protocol quic
2023-04-23T12:31:39Z ERR update check failed error=“Get "https://update.argotunnel.com?arch=amd64&clientVersion=2023.4.1&os=linux": dial tcp: lookup update.argotunnel.com on 127.0.0.11:53: read udp 127.0.0.1:36858->127.0.0.11:53: i/o timeout”
2023-04-23T12:31:39Z INF ICMP proxy will use 172.28.0.2 as source for IPv4
2023-04-23T12:31:39Z INF ICMP proxy will use :: as source for IPv6
2023-04-23T12:31:39Z INF Starting metrics server on 127.0.0.1:38105/metrics
2023-04-23T12:31:59Z INF Tunnel server stopped
2023-04-23T12:31:59Z ERR Initiating shutdown error=“Couldn’t resolve SRV record &{region1.v2.argotunnel.com. 7844 1 1}: lookup region1.v2.argotunnel.com. on 127.0.0.11:53: read udp 127.0.0.1:41332->127.0.0.11:53: i/o timeout”
2023-04-23T12:31:59Z INF Metrics server stopped
Couldn’t resolve SRV record &{region1.v2.argotunnel.com. 7844 1 1}: lookup region1.v2.argotunnel.com. on 127.0.0.11:53: read udp 127.0.0.1:41332->127.0.0.11:53: i/o timeout
Docker-Compose:
version: “3.9”
services:
cloudflared:
container_name: cloudflared
image: Cloudflare/cloudflared:2023.4.1
restart: unless-stopped
command: tunnel --no-autoupdate run --token $TUNNEL_TOKEN
Lastly, there is a related article titled (but with no solution):
“Error when trying to set up Cloudflare tunnel in docker”