DHCP/DNS detection seems not to be stable

[dodmi]

I'm using the latest Windows x64 release and I'm trying to get DHCP/DNS detection to work.
.\dnscrypt-proxy.exe --version returns 2.1.8

On dnscrypt-proxy startup, I get multiple entries of the following kind:
[2025-03-27 21:40:26] [NOTICE] Starting a DHCP/DNS detector for IPv4 [2025-03-27 21:40:26] [NOTICE] Starting a DHCP/DNS detector for IPv4 [2025-03-27 21:40:26] [CRITICAL] Failed to start the DHCP/DNS IPv4 server: listen udp4 192.168.178.27:68: bind: Normalerweise darf jede Socketadresse (Protokoll, Netzwerkadresse oder Anschluss) nur jeweils einmal verwendet werden.

netstat -a | Select-String ":68" returns nothing, so nothing seems to be listening on port 68.

I've configured a forwarding rule to use $DHCP to resolve a domain. Pinging the domain works sometimes, but not doesn't in most cases. Resolving other domains works flawlessly.

Can anyone give me some hints, what I'm doing wrong?

[lifenjoiner]

#2814 is submitted.

[dodmi]

Is this the same code as in your fork: #2368 (comment) ?
It‘s been working flawlessly for years now, and I‘m still using it and it seems to work much better (the forwarded domains are resolved everytime, not only sometimes)

[lifenjoiner]

Frankly, I don't know. You can try and compare. They use the same lib, but have different (fallback) strategies.

[dodmi]

I‘m doing so. I guess you won‘t backport later changes, so I need to choose, if your fix doesn‘t improve detection?

[kan-ibal]

Is $DHCP is suppose too be working in 2.1.12? For me it does not work at all (2 different systems, NetworkManager and Conman).
Is it possible to implement $RESOLV variable that is configured as link to resolv file already created from DHCP.

[dodmi]

I'm still using @lifenjoiner's version, based on version 2.1.5 on Windows. I stopped testing, since there were no notable changes concerning the dynamic DHCP function in the implementation.