Service:MyPC, Algorithm: Priority WAN1/WAN2: Source: 192.168.1.44, Destination: Any, Prot/Port: Any
Service:Default, Algorithm: Enforced WAN2
When WAN1 & WAN2 are both up all DNS queries are via WAN2 (which is what I want).
My problem is that when WAN2 fails the DNS queries are going via WAN1 (for queries from my PC on 192.168.1.44).
It is the 2nd rule that is routing DNS queries to WAN1 (since if I disable this rule then DNS queries fail when WAN2 is down, which is what I want).
Based on the assumption that 1st match is used I don’t see that the 2nd rule (or any others) should have any effect because the 1st rules is a match (regardless of the destination WAN connection being down).
You have enforced DNS Protocol to WAN2. so in any case it goes through WAN2. if WAN2 fails your DNS query fails also. this is a normal behavior of enforced policy.
in WAN configuration pages, you should have configured DNS Server IP addresses there. Peplink will add the system weighted balance outbound rules for those DNS servers on top of the user defined Custom Rules.
If the computer are querying the public DNS server directly which same as the DNS configured in WAN Connection page, the DNS query will follow the system outbound rules. Therefore, it won’t meet your enforce rule.
If the computer are querying DNS through Peplink’s LAN IP (Peplink DNS proxy), it will not go through Outbound Policy.