On my self-compiled openwrt, in https-dns-proxy.log I see many errors, originating from curl.
Likely, when having outstanding DoH-requests to upstream resolver Quad9, and a new request arrives at proxy.
Attached you find 2 log files with errors, the names of which indicate time stamp of an error example.
err1_at_1776414303.log.gz
err2_at_1776414512.log.gz
Errors are recovered due to retries of dnsmasq, though.
https-dns-proxy -V
2025.12.29-r4
Using: ev/4.33 c-ares/1.34.6 libcurl/8.19.0 mbedTLS/3.6.5 nghttp2/1.66.0
Features: HTTP2 HTTPS-proxy IPv6
Addendum: Same effect also, when using OpenSSL
https-dns-proxy -V
2025.12.29-r4
Using: ev/4.33 c-ares/1.34.6 libcurl/8.19.0 OpenSSL/3.5.5 nghttp2/1.66.0
Features: HTTP2 HTTPS-proxy IPv6
On my self-compiled openwrt, in https-dns-proxy.log I see many errors, originating from curl.
Likely, when having outstanding DoH-requests to upstream resolver Quad9, and a new request arrives at proxy.
Attached you find 2 log files with errors, the names of which indicate time stamp of an error example.
err1_at_1776414303.log.gz
err2_at_1776414512.log.gz
Errors are recovered due to retries of dnsmasq, though.
https-dns-proxy -V
2025.12.29-r4
Using: ev/4.33 c-ares/1.34.6 libcurl/8.19.0 mbedTLS/3.6.5 nghttp2/1.66.0
Features: HTTP2 HTTPS-proxy IPv6
Addendum: Same effect also, when using OpenSSL
https-dns-proxy -V
2025.12.29-r4
Using: ev/4.33 c-ares/1.34.6 libcurl/8.19.0 OpenSSL/3.5.5 nghttp2/1.66.0
Features: HTTP2 HTTPS-proxy IPv6