@johnpoz I admit the setup isn't ideal, however somehow despite the error messages the system seems to work -- clearly I don't really understand all the underpinnings of how things work.
How should I be constructing things??
Two pfsense installations running unbound with same domain. Each pfsense installation has domain overrides for subdomains running on their installation. Additionally each pfsense answering DNS over DOT on port 853.
domain.com------->>>Pfsense #1 (domain=domain.com) -> Overrides--->test.domain.com
--->test2.domain.com
--->test3.domain.com
------>>>Pfsense #2 (domain=domain.com) -> Overrides --->test4.domain.com
--->test5.domain.com
--->test6.domain.com
Each installation can resolve locally, however if pfsense installations connected by vpn, I need name resolution for devices on Pfsense #1 network accessible to devices on Pfsense#2 network -- and vice versa. If VPN is broken or down, local domain overrides will still work.
I'm just making use right now of the unbound domain overrides section similar to this:
Screenshot 2025-01-01 at 5.40.14 PM.png
In terms of DOT -- no I don't need it between the pfsense nodes on either end of the tunnel -- however how do I have it only active for LAN clients but not for the tunnel?
I'm not looking actually to forward DNS requests, rather have unbound "resolve" them and then pass the answer back to the clients. In terms of resolving (not forwarding), how does each unbound server know what DNS server is definitive for a specific local domain that's split? I thought I was accomplishing this by listing the servers within the domain overrrides section.