31
22.1 Legacy Series / Re: [SOLVED] Unbound not responding?
« on: March 08, 2023, 06:50:21 pm »So that was apparently the answer--set Unbound's outgoing interface to WAN rather than all. It seems that with that set to all, Unbound expects to be able to communicate over IPv6, which it can't do, and therefore fails. A couple of things that didn't work, without setting the interface to WAN:What I still don't understand is why pfSense worked--as far as I can tell, it has all the same buttons, switches, and knobs, and it uses most of the same underlying software. And my pfSense box was set to "all" for the outbound interface, and it worked fine. So I'm not sure why the difference is there, but it's working, so good enough at least for now.
- Explicitly disabling IPv6 on LAN. It defaulted to "track interface," whatever that means; I'd suspected that explicitly disabling IPv6 on this interface (as it already was on WAN) might result in Unbound realizing that it can't communicate over IPv6 and reverting to IPv4. It didn't seem to change anything.
- Enabling DHCP6 on WAN. I don't use IPv6 (I have a static IPv4 address), but my ISP will give me an IPv6 address if I ask for it. But enabling this also didn't have Unbound working.
what would happen if you have local forwarding (other DNS servers resolving internal domains), and you use different interfaces to reach them. Would that be broken with "outgoing = WAN"?