DNS list moves/changes when rerunning the wizard



  • Before re-running wizard:
    DNS server(s)
    127.0.0.1
    8.8.8.8
    75.75.75.75
    8.8.4.4
    75.75.76.76

    After:
    DNS server(s)
    127.0.0.1
    75.75.75.75
    8.8.4.4
    75.75.76.76
    8.8.8.8

    I made no changes, just clicked through. iirc, I'll end up with multiple 8.8.8.8 entries if I run the wizard enough times.



  • Going through the wizard again may change the order of the DNS servers in the config depending on what you had configured before running it (if more than 2 are configured, the order changes).



  • Okay, thanks. Wasn't sure if this was expected behavior or a bug.


  • LAYER 8 Global Moderator

    I really don't get that config at all..  Why not just point to 127.0.01 and be done with it, be it you are using the forwarder or the resolver letting pfsense point local and letting the name service your running resolve both local and remote seems like a better setup to me.

    If your name service goes down on pfsense, you most likely have bigger issues than if pfsense can resolve www.google.com



  • The 127.0.0.1 isn't an entry I configured, it's just what I copied and pasted out of the dashboard.

    My assumption has been (perhaps incorrectly) that whatever DNS servers I configure in pfsense are ultimately where the DNS daemon will go for resolution before caching the answer.



  • Well, just tested and indeed found I assumed incorrectly.


  • LAYER 8 Global Moderator

    127.0.0.1 should really the only entry you see in the dashboard.  see mine attached, atleast when using the resolver.. Which is the default.




  • @johnpoz:

    127.0.0.1 should really the only entry you see in the dashboard.  see mine attached, atleast when using the resolver.. Which is the default.

    Only when you have no DNS servers specified under System>General Setup and have no dynamic WAN types that assign DNS or have acceptance of dynamically assigned DNS disabled. Most systems will end up with multiple servers listed, though yes with Unbound configured at defaults, that's not necessary.



  • What with this 2.2.6 stuf?  Thought this was the 2.3 beta board.  ;)



  • @NOYB:

    What with this 2.2.6 stuf?  Thought this was the 2.3 beta board.  ;)

    Didn't catch that. Yeah c'mon johnpoz, time to upgrade. :)


Log in to reply