Open skedastically opened 1 day ago
Use a different --dns-option
in the container to disable forcing TCP queries. For me an empty comment (#
) to be inserted into options
would works fine.
podman-compose.yml
:
services:
uptime-kuma:
...
dns_opt: ["#"]
$ podman exec uptime-kuma cat /etc/resolv.conf
search dns.podman
nameserver 192.168.80.1
nameserver fdfc:3c2c:255c:c286::1
options #
π I have found these related issues/pull requests
.
π‘οΈ Security Policy
Description
When configuring DNS over TCP using the
options use-vc
option, Uptime Kuma fails to resolve any domains and red out on all HTTP(s) monitors. This seems to be caused by DNS over TCP not being supported by Uptime Kuma.π Reproduction steps
/etc/resolv.conf
on host as follows:Container's
/etc/resolv.conf
:π Expected behavior
DNS will resolve normally and Uptime Kuma works as before.
π Actual Behavior
The following was logged. Same errors also shown on web UI.
The following commands inside the container also fails:
Peculiarly, curl works when IPv4 or IPv6 is specified:
π» Uptime-Kuma Version
1.23.15
π» Operating System and Arch
Linux aarch64
π Browser
Firefox
π₯οΈ Deployment Environment
π Relevant log output
No response