Multiwan and DNS Resolver

dpa

Hello,

I have 3 WANs and running DNS Resolver. I noticed that when 1 WAN goes offline, clients in the LAN side are getting DNS issues on their browsers. It will take a couple of page refresh/reload for the page to load. Loading web pages in general is very slow.

System/Routing/Gateways settings:
Default gateway IPv4 = Multiwan group (all three)

DNS Resolver settings:
Enable Forwarding Mode = unchecked
Outgoing Network Interfaces = all three WANs

Been reading a lot regarding Unbound and best practices, but I still don't have a clue on this issue. I would be grateful if someone can help me on this.

Thanks a lot.

kiokoman

@jimp one time said:

We recommend forwarding mode for unbound [only when used with Multi-WAN] because then it could respect a static route for specific forwarders for each WAN. Otherwise it would always send requests to the roots via the default WAN even if it was down.

https://forum.netgate.com/topic/81789/unbound-and-multi-wan-forwarder-explanation

Probably still true

dpa

@kiokoman Oh! I must have missed this thread. Thanks! Hopefully someone from the dev will clarify this for us. :)

jimp

If your default gateway group is a failover group (every gateway on a different tier) then it should still work in resolver mode since the default gateway should always be present & up.

dpa

@jimp said in Multiwan and DNS Resolver:

If your default gateway group is a failover group (every gateway on a different tier) then it should still work in resolver mode since the default gateway should always be present & up.

Thanks @jimp! I set the default gateway to the 3 WAN group with the same tier. I was with the understanding that same tier will also do failover when one goes offline.

jimp

For policy routed traffic, yes. But default gateway switching doesn't support load balancing, only failover.

dpa

@jimp said in Multiwan and DNS Resolver:

For policy routed traffic, yes. But default gateway switching doesn't support load balancing, only failover.

Yes I can now confirm this. Thank you @jimp! Now my DNS Resolver is working flawlessly.