Feature #5549

Additional DNS entries in General Setup would be good for 3 or more WAN's

Added by Eduard Rozenberg over 1 year ago. Updated about 2 months ago.

Web Interface
Target version:
Start date:
Due date:
% Done:



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.


#1 Updated by Bipin Chandra over 1 year ago

+1 and so far i used a modified system.php file adding more of those and they get properly saved in the config and also used by the system

#2 Updated by Michael Kellogg 3 months ago

this is true add ipv6 and it has even more need

#3 Updated by Kill Bill 3 months ago

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.

#4 Updated by Jim Pingle 3 months ago

That's for the host resolver itself -- dnsmasq and unbound in forwarding mode will pick up more.

#5 Updated by Kill Bill 3 months ago

Yup. It'd be awesome if those settings were moved to the relevant place (i.e., DNS forwarder/resolver settings). This thing is just causing perpetual user confusion. Some description improvements here:

#6 Updated by Phillip Davis 3 months ago

It seems to work too easily, what have I forgotten?

#7 Updated by Renato Botelho 3 months ago

  • Status changed from New to Feedback
  • Assignee set to Renato Botelho
  • Target version set to 2.4.0
  • % Done changed from 0 to 100

PR has been merged, thanks!

#8 Updated by Phillip Davis 2 months ago

Note: I kept this in the General Setup page where it has been since eternity. Just made it so a variable number of DNS Servers can be entered. (Kill Bill mentioned moving the UI for this elsewhere)

#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 '' server which is on a directly connected network.
A gateway can not be assigned to DNS '' server which is on a directly connected network.

2.3.3-DEVELOPMENT (amd64) 
built on Fri Jan 13 14:45:19 CST 2017
FreeBSD 10.3-RELEASE-p15

#10 Updated by Michael Kellogg 2 months ago

that error happens re-saving current setup with 4 dns servers

#11 Updated by Michael Kellogg 2 months ago

ok already had manually added staic route for and causes failure in error checking

#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.


#14 Updated by Jim Pingle about 2 months ago

  • Category set to Web Interface
  • Target version changed from 2.4.0 to 2.3.3

Also available in: Atom PDF