https-dns-proxy is blocking DS-Lite reconnections

[Nmrawe]

I have a problem with the DS-Lite connections being blocked when reconnecting: openwrt/openwrt#18092.

This issue doesn't happen when https-dns-proxy is not running. But If it is, https-dns-proxy needs to be stopped and started again (reloading or restaring won't help).

Probably https-dns-proxy is blocking DNS connections to AFTR domains used by DS-Lite.

https-dns-proxy 2023.12.26-r4

[Nmrawe]

As a workaround, added

service https-dns-proxy stop
sleep 5
service https-dns-proxy start

to

proto_ipip6_teardown() {
        local cfg="$1"
}

and

proto_dslite_teardown() {
        local cfg="$1"
}

in /lib/netifd/proto/dslite.sh.

It seems to work fine, at least in case of manually restarting the interface as I don't know when my ISP is gonna trigger the prefix change.

[stangri]

Probably https-dns-proxy is blocking DNS connections to AFTR domains used by DS-Lite.

Configure these domains to be resolved with your ISP's resolver.

[Nmrawe]

As list server in the dhcp file? It doesn't seem to fix this issue.

[stangri]

Does the issue persist if you use any non-encrypted DNS resolver other than your ISP's resolver (like Google, Cloudflare) without https-dns-proxy?

[Nmrawe]

No, I don't use my ISP's resolver at all.

[stangri]

Adding proper entries to have the domains resolved without https-dns-proxy should help then.

[Nmrawe]

DS-Lite may not like 127.0.0.1 in list server. Sadly, I am unable to do more testing right now as I'm still waiting (almost 11 days so far) for the prefix change to check my workaround.