@GruensFroeschli:
Then how should LAN1 users resolve names when WAN2 is down?
If that happens, Internet will go down anyway. Therefore I just have to change the rules of the firewall to route the packets through the last gateway available and then try to resolve the problem.
@GruensFroeschli:
IMO the "correct" way to do this is:
Set on the pfSense as primary and secondary DNS entry: 208.67.222.222 and 208.67.220.220
Like this all requests go to WAN1.
Then create a static route for 208.67.220.220 pointing to WAN2.
Like this all requests go to WAN1, and when WAN1 is down all requests go to WAN2.
That's pretty much like the loadbalancing. I was interested in this method. But i'm not supposed to do something like that.
@GruensFroeschli:
If you want that users resolve names over different WANs depending on in which LAN they are you have to stop using the DNS-forwarder and set the DNS entries on the clients direct (DHCP or static).
The fact is, I've opened access for LAN to WAN2 Network (Just for the local network, and not to access the Internet) which is why i used both WAN and WAN2 modem's addresses as global DNS. LAN Users have the IP address of pfsense as DNS, whereas LAN2 users have a static address: the address of the WAN2 modem.
This seems to do the trick.
