[BUG] https-dns-proxy: Update to commit "b499aa9" to resolve "ares_process_fds: symbol not found" Issue

[coralsundy]

Package Name

https-dns-proxy

Maintainer

@stangri (OpenWRT Pkg Maintainer)
@aarond10 (Upstream Pkg Maintainer)

OpenWrt Version

24.10.0

OpenWrt Target/Subtarget

Linksys E8450 / Belkin RT3200 (assume MT7622BV / aarch64_cortex-a53)

Steps to Reproduce

1. On Linksys E8450, install 24.10.0 version.
2. Install https-dns-proxy version 2025.10.07-r1 (which is latest as of writing)
3. See this issue for all the errors, not happening on an older 2025.05 version I believe. This issue was initially opened on aarond10/https_dns_proxy repo: [BUG] Linksys E8450 / Belkin RT3200 fail to start on https-dns-proxy_2025.10.07-r1_aarch64_cortex-a53.ipk aarond10/https_dns_proxy#198

Actual Behaviour

Service start normally, will not error out and stop.

The reason I open this issue is because upstream has fixed the issue already in aarond10/https_dns_proxy@b499aa9 but openwrt needs to update the builds with the commit here:

packages/net/https-dns-proxy/Makefile

Lines 8 to 16 in ad2477e

	PKG_SOURCE_PROTO:=git
	PKG_SOURCE_URL:=https://github.com/aarond10/https_dns_proxy/
	PKG_MIRROR_HASH:=2d0e5f031c8de7f42fa7f2e79d5638f9e4899c056d710fc3638a03112b383be5
	PKG_SOURCE_VERSION:=7b27ecd5598d03bbe79651cc80efca886d433cd9
	PKG_MAINTAINER:=Stan Grishin <stangri@melmac.ca>
	PKG_LICENSE:=MIT
	PKG_LICENSE_FILES:=LICENSE

Since I am not familiar with how OpenWrt build packages, I open this issue asking for help. Right now there is no way to revert to an older version, so I am using my Internet Providers DNS at the moment. Thanks.

Confirmation Checklist

• The package is maintained in this repository.
• I understand that issues related to the base OpenWrt repository or LuCI repository will be closed.
• I am reporting an issue for OpenWrt, not an unsupported fork.

[coralsundy]

I will also try to update my openwrt to latest stable 24.x to check further.

[stangri]

I will also try to update my openwrt to latest stable 24.x to check further.

Please try the current https-dns-proxy package on the most recent stable (24.10.4, not 24.10.0) or current RC and update this.

[coralsundy]

After upgrading to 24.10.5 which is the latest patch as of now it resolved. Will close this issue for now. Thanks.