Https-dns-proxy crash after upgrade

I did owut upgrade with all packages baked in to one image. It was working fine till 25.12.3. anymore. I cannot restart the daemon. I hard coded DNS entries in to wan and wan6 and quad 9 is working but I am not getting https DNS


Model	Linksys MX4300
Architecture	ARMv8 Processor rev 4
Target Platform	qualcommax/ipq807x
Firmware Version	OpenWrt 25.12.4 r32933-4ccb782af7 / LuCI openwrt-25.12 branch 26.134.75701~cd18b8e
Kernel Version	6.12.87
[May 16, 2026, 10:14:57 PM PDT] daemon.info: https-dns-proxy[9073]: [F] 1778994897.372296 dns_server.c:33 Error binding on 127.0.0.1:5053 UDP: Address in use (98)
[May 16, 2026, 10:15:02 PM PDT] daemon.info: https-dns-proxy[9238]: [F] 1778994902.432238 dns_server.c:33 Error binding on 127.0.0.1:5053 UDP: Address in use (98)
[May 16, 2026, 10:15:07 PM PDT] daemon.info: https-dns-proxy[9282]: [F] 1778994907.471464 dns_server.c:33 Error binding on 127.0.0.1:5053 UDP: Address in use (98)
[May 16, 2026, 10:15:12 PM PDT] daemon.info: https-dns-proxy[9320]: [F] 1778994912.521965 dns_server.c:33 Error binding on 127.0.0.1:5053 UDP: Address in use (98)
[May 16, 2026, 10:15:15 PM PDT] user.notice: https-dns-proxy [9358]: Starting https-dns-proxy 2026.03.18-r3 instances ✓✓
[May 16, 2026, 10:15:15 PM PDT] user.notice: https-dns-proxy [9358]: Updating notrack rules ✓
[May 16, 2026, 10:15:15 PM PDT] user.notice: https-dns-proxy [9358]: Setting trigger for wan ✓
[May 16, 2026, 10:15:15 PM PDT] daemon.info: https-dns-proxy[9487]: [F] 1778994915.321785 dns_server.c:33 Error binding on 127.0.0.1:5053 UDP: Address in use (98)
[May 16, 2026, 10:15:20 PM PDT] daemon.info: https-dns-proxy[9660]: [F] 1778994920.391607 dns_server.c:33 Error binding on 127.0.0.1:5053 UDP: Address in use (98)
[May 16, 2026, 10:15:20 PM PDT] daemon.info: procd: Instance https-dns-proxy::instance1 s in a crash loop 6 crashes, 0 seconds since last crash
[May 16, 2026, 10:15:40 PM PDT] user.notice: https-dns-proxy [9852]: Starting https-dns-proxy 2026.03.18-r3 instances ✓✓
[May 16, 2026, 10:15:40 PM PDT] user.notice: https-dns-proxy [9852]: Updating notrack rules ✓
[May 16, 2026, 10:15:40 PM PDT] user.notice: https-dns-proxy [9852]: Setting trigger for wan ✓
[May 16, 2026, 10:15:40 PM PDT] daemon.info: https-dns-proxy[9981]: [F] 1778994940.381226 dns_server.c:33 Error binding on 127.0.0.1:5053 UDP: Address in use (98)
[May 16, 2026, 10:15:40 PM PDT] daemon.info: procd: Instance https-dns-proxy::instance1 s in a crash loop 7 crashes, 0 seconds since last crash
[May 16, 2026, 10:17:00 PM PDT] user.notice: https-dns-proxy [10612]: Starting https-dns-proxy 2026.03.18-r3 instances ✓✓
[May 16, 2026, 10:17:01 PM PDT] user.notice: https-dns-proxy [10612]: Updating notrack rules ✓
[May 16, 2026, 10:17:01 PM PDT] user.notice: https-dns-proxy [10612]: Setting trigger for wan ✓
[May 16, 2026, 10:17:01 PM PDT] daemon.info: https-dns-proxy[10748]: [F] 1778995021.151750 dns_server.c:33 Error binding on 127.0.0.1:5053 UDP: Address in use (98)
[May 16, 2026, 10:17:01 PM PDT] daemon.info: procd: Instance https-dns-proxy::instance1 s in a crash loop 8 crashes, 0 seconds since last crash

Reason explained ?

Check the config of https-dns-proxy every instance must have its own listen port