Additional DNS entries in General Setup would be good for 3 or more WAN's
For multi-wan with 3 or more WAN's, it would be good to have additional DNS server fields in General Setup.
Currently there are 4 possible entries.
With 3 WAN's for example, assigning 2 different DNS servers to each of the WAN gateways would require 6 total entries in General Setup
because pfSense recommends that each gateway be assigned its own unique DNS servers.
Maybe someone could instead fix/nuke the misleading note from the GUI, instead of putting in more DNS servers that will never get used for anything? (Cf. https://github.com/freebsd/freebsd/blob/master/include/resolv.h#L128)
#9 Updated by Michael Kellogg 2 months ago
getting this error whe trying to add more dns servers
A gateway can not be assigned to DNS '188.8.131.52' server which is on a directly connected network.
A gateway can not be assigned to DNS '184.108.40.206' server which is on a directly connected network.
built on Fri Jan 13 14:45:19 CST 2017
#12 Updated by Phillip Davis 2 months ago
So that sort of config should have failed the input validation already prior to his change. The code considers anything on a "really locally connected" network or pointed to by a static route in the config to be "local" and a DNS server on such a network/address should not have a gateway specified.
I guess it would be possible to do more validation checks, and if the existing static route for that address already points out the selected gateway, then it is OK. But actually it is easy for the user to either remove the static route or not select a gateway for the DNS server (and then it will use the static route they already set up).
#13 Updated by Jim Pingle 2 months ago
- Status changed from Feedback to Resolved
This seems to work fine as-is. No need to check/validate someone's unintentional misconfiguration. At least it did error (correctly) rather than trying to clobber the route.
I've been running with this for a few days and haven't seen any problems. Seems solid to me.