Topics

I have configured a DNS zone for a domain (e.g., example.com) to resolve the servers on my intranet, and I want any other hosts that are not defined in BIND to be resolved using the Cloudflare DNS settings for the same domain (example.com).
 How can I configure BIND on OPNsense for the intranet to achieve this?

I have OPNsense version: 22.1.8_1-amd64
I setup WireGuard on the OPNSense box with tho WAN and I am able to connect and access the LAN side hosts, etc. However, it only works with the WAN which is currently the default gateway. If that WAN is down, then OPNSense switches the default gateway (gateway switching is enabled) and WireGuard peers can utilize the 2nd WAN to connect. However, as long as WAN1 is "up", peers cannot connect to WAN2. Well, actually the peers appear to be able to connect to WAN2 but traffic isn't properly received (a few bytes are received but no network services such as ping, ssh, etc. work).

Can anyone point me in the right direction of how to setup WireGuard on OPNSense such that peers can connect to either WAN interface?

I need some advice on OPNsense updates.
I plan to use OPNsense as a replacement for a real production router.
I hesitate to apply updates due to the risk of bugs that could affect OPNsense functionality.
What is the best strategy for applying updates to a production OPNsense router?