OPNsense Forum

Archive => 21.1 Legacy Series => Topic started by: edz on March 25, 2021, 01:52:55 am

Title: Multi WAN & Unbound
Post by: edz on March 25, 2021, 01:52:55 am

I have followed the instructions of setting up Multi WAN, including the steps of adding DNS Servers to each Gateway group.

How does this work when using Unbound?  Does all traffic that is destined for a Gateway Group use the gateway DNS?  Is there anyway to use Unbound instead of external DNS Servers when using Multi WAN?

Title: Re: Multi WAN & Unbound
Post by: tong2x on March 25, 2021, 01:54:57 am

you need to use local DNS else your conenction will go crazy

it will be OPNsense that will negotiate the connection I believe

Title: Re: Multi WAN & Unbound
Post by: edz on March 25, 2021, 01:57:07 am

If I put a local DNS server against a gateway group I get:

You can not assign a gateway to DNS server "192.168.1.1" which is on a directly connected network.

Title: Re: Multi WAN & Unbound
Post by: tong2x on April 07, 2021, 04:31:43 pm

screen shot?

Title: Re: Multi WAN & Unbound
Post by: tong2x on April 07, 2021, 04:42:12 pm

in each gateway you can assign a monitor ip. which opnsense uses to detect if the gateway is down(if option is selected)

in system-setting-general
1) you need to allow gateway switching
2) for each gateway assigned a unique dns server(external, like google, open, fast dns, ubound will use this as a forwarding dns server, if selected)
3) you need to have a local dns server for your client which is ubound. you bound will then use the assign dns for each gateway as a forwarding dns (you can choose a restrictive dns server if say you want to block porn or malware)
of course you will still need to define which gateway to use... by default opnsense will choose 1 (not multiwan, hence you need a multiwan group to tell opnsense how the gateways will interact with each other