unbound: outgoing network interfaces

[crt333]

I'm running 21.7.4 on a Quotom box, its been running great for years. Besides WAN I have two WG tuinnels set up, and I always had unbound configured to use these WG tunnels instead of WAN for DoT lookups. That worked until this upgrade, if WAN isn't selected unbound doesn't work. I'd prefer my DNS lookups to go out over the WG rather than through my ISP, any suggestions?

If I could get AdGuard to query over WG I wouldn't need unbound, but this has been my solution until now, with adguard asking unound on 5353.

[Greelan]

That’s interesting. Just a couple of days ago someone else found that option was not helping with sending unbound queries over WG too.

Are you able to raise a GitHub issue? It seems 21.7.4 broke something. It may even be a broader issue with how it deals with interfaces (perhaps explaining the odd list of unassigned interfaces that now appears in Interfaces/Overview).

[crt333]

I will enter a github issue, thanks.

[Patrick M. Hausen]

The outgoing network interface is determined by the target IP address and the routing table and nothing else. Unless an explicit "force gateway" rule is used.

[crt333]

I haven't done a force gateway rule anywhere, and what you say may be true, but I can tell you for certain that the selection in Services->Unbound DNS->General for "Outgoing Network Interfaces" matters because if I remove WAN and select WG1 and WG2 it doesn't work, and it did before 21.7.4.

[crt333]

same behavior (outgoing unbound network interfaces over WG don't work) in 21.7.5