Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Multi-WAN DNS Servers

    Scheduled Pinned Locked Moved Routing and Multi WAN
    4 Posts 2 Posters 2.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      ScorchedHands
      last edited by

      Obviously you can have as many "WAN" connections on pfSense as you want, my question is about the DNS entries those connections.  Under General Setup you only have room for 4 dns servers.  Assuming I only use one for each WAN connection, this really limits me to 4 WAN connections.  Is there another way to configured DNS servers for WAN connections or is there any way we can increase this number?  The entry should really be an expandable list like there are in so many other parts of the system IMHO.  I could probably get away with simply not putting in DNS for the additional connections but in the interest of completeness I would like the option.

      Also on an unrelated note.  When pfSense has no active internet connection but has a DNS server configured that is not accessible any page that requires a DNS lookup (ie: Dashboard's Update Check) hangs for a long time and whole webconfigurator hangs.  I figured this might have been part of the reason why localhost was added as the primary dns server for the router which would then proxy the dns queries to the other configured dns servers but this does not seem to be making any difference.

      1 Reply Last reply Reply Quote 0
      • P Offline
        podilarius
        last edited by

        Unless your DNS server only responds to your IP, then even if the link is down, the other links can still carry the DNS lookups to your other carriers. I agree that having the ability to add more DNS would be okay. You can also use national servers like the 2 google and the 2 AT&T (8.8.8.8, 8.8.4.4, 4.2.2.2, and 4.2.2.1) and all your carriers would work and you would not have a long list of DNS servers to try, keeping lookup times down.

        1 Reply Last reply Reply Quote 0
        • S Offline
          ScorchedHands
          last edited by

          I know it's been a while, and I forgot about this post until just now since I didn't get the reply email.

          I think the issue that comes in with trying to share the configured DNS servers between WAN connections is if you set a gateway for them.  If you do not set a gateway for them, does the system use the default gateway then instead?  In which case before they would stop working when the default gateway went down, of course now in 2.0.1 we have the neat option to have the default gateway switch with failovers which should solve that problem if it exists.

          1 Reply Last reply Reply Quote 0
          • P Offline
            podilarius
            last edited by

            Yes,if you don't set a gateway it will try the default. It should switch with failures as you mentioned. However; unless there is some dyer need for using ISP assigned DNS server, I would use a national one or public one. I would even go so far as to setup 2 of my own before using so many ISP based DNS servers.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.