Multi-WAN - Strange DNS Issue - Need Help

[fearz]

Hi,

I'm having a very strange DNS issue that i'm unable to resolve.

I have 2 WAN connections (WAN1 - 192.168.6.1 - Primary & WAN2 - 192.168.5.1 - Secondary)

I have WANGRP consists of both WAN interfaces and a firewall rule set the default gateway as WANGRP so that I combine both connections and benefit from the speed.

In System, Gateways, If I choose WAN1 as an Upstream Gateway (checkbox) DNS won't resolve, however the connection is up.

If I choose WAN2 as an Upstream Gateway (checkbox) DNS works fine.

I need to choose WAN1 (primary) to have DNS resolve...I'm about to go crazy as to what would be causing this.

Please let me know of any settings/configurations you might need to know so we can solve this.

Thanks

[cooljimy84]

I getting something like this, if i tell unbound to go out on WAN2 it works, if i set it to WAN1 it looks like it sends in the logs but never gets a responce. If i quirey an internal name or override name it resolves fine. Looking at my nextdns logs the quiery never makes it to them.

If i select both WANs it takes ages to resolve (prob timing out on one interface then moving over)

this is since the update i did this morning.

My stupid fault, i had some wonky firewall rule that didn't get loaded till the reboot