When local dns server is listening at :53 and resolv.conf points to it, the first connectivity check will fail. This is because when we use the local dns server to resolve the domain name of the node, the dae is not yet listening, but the ebpf program has been installed and dns request is redirected to dae, so the first dns request will fail.
If we add local dns servers to must_direct list, dns leaking possibly occurs.
⏳ dae-wing (origin/main) is currently out-of-sync to dae (origin/main); changes are proposed by @dae-prow-robot in actions - https://github.com/daeuniverse/dae-wing/actions/runs/7489668234
418 - fix/docs: fix the first check failure and possible dns leaking
PR: https://github.com/daeuniverse/dae/pull/418
Context:
When local dns server is listening at :53 and resolv.conf points to it, the first connectivity check will fail. This is because when we use the local dns server to resolve the domain name of the node, the dae is not yet listening, but the ebpf program has been installed and dns request is redirected to dae, so the first dns request will fail.
If we add local dns servers to must_direct list, dns leaking possibly occurs.