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

    Pfsense 2.3 DNS server issue

    Scheduled Pinned Locked Moved IPsec
    3 Posts 2 Posters 1.2k 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.
    • G
      george203
      last edited by

      Hello,

      First of all, congrats on the new pfSense release! It's looking great. We have a small issue since we upgraded from pfSense 2.2.2 to 2.3 yesterday. Surprisingly, out VPN is working properly tied to LDAP authentication, so the core functions are alright and we are able to authenticate.

      We were using a normal VPN tunnel, not a full tunnel, so the internet traffic was not passed through the firewall. We are relying on the firewall to provide local DNS servers to mobile clients, so that they can solve the all our local DNS entries in active directory.

      This is where things are not working anymore, as pfSense provides the DNS servers to our Shrewsoft clients, however we cannot access anything by name anymore. When performing an nslookup through windows, our local DNS servers should do the lookup, but now the DNS that is set up on the client seems to be doing that. So from what it seems, the DNS settings from Shrewsoft are not being pushed as default and primary.

      Firewall logs do not show anything on this.

      Has anyone encountered this problem ?

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        You probably need the Unity plugin enabled I'm guessing. VPN>IPsec, Advanced, enable Unity there. Stop then start (not restart) the service afterwards just to make sure it's applied and everything is forced to reconnect.

        1 Reply Last reply Reply Quote 0
        • G
          george203
          last edited by

          Thank you for your help. Unfortunately I had to revert back to 2.2.2 because of this, as it's a production environment, but I will try again on the first occasion and let you know.

          Never realized that a plug in was required in the new version.

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