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

    Newbie DNS forwarder issue

    Scheduled Pinned Locked Moved DHCP and DNS
    6 Posts 4 Posters 2.1k 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.
    • A Offline
      atakacs
      last edited by

      Folks

      I'm sure I'm missing something fairly obvious - pretty new with pfS, please bear with me…

      Just installed 2.1.2 on a Vmware box. My setup is fairly basic, one static WAN IP, one NATed LAN and one OPT LAN that might become by DMZ (not an issue for the moment).

      Everything seems to work except for DNS forwarding

      My LAN clients do get a DCHP lease, the DNS server is set to 172.16.100.254 but they will not resolve anything. Note the pfS itself seems to have issues (can't check update status message and local (console) resolver test fails. If I set an explicit external DNS everything works fine.

      Logs don't show anything obvious to my untrained eyes

      What am I missing ?

      1 Reply Last reply Reply Quote 0
      • jimpJ Offline
        jimp Rebel Alliance Developer Netgate
        last edited by

        Did you set any option on Services > DNS Forwarder? Maybe selected a listening interface? If so, make sure at least both LAN and Localhost are selected.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • K Offline
          kpa
          last edited by

          I ran to the same snafu when I installed Unbound to replace the built-in DNSMasq. If you don't set it to listen on localhost nothing that runs on the pfSense system can resolve addresses (or resolves very slowly) because /etc/resolv.conf has 127.0.0.1 as the first nameserver.

          1 Reply Last reply Reply Quote 0
          • jimpJ Offline
            jimp Rebel Alliance Developer Netgate
            last edited by

            I added some checks/code to 2.2 to disable the 127.0.0.1 line in resolv.conf if the DNS Forwarder/Resolver are set to listen but not to Localhost to avoid that situation in the future.

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • A Offline
              atakacs
              last edited by

              Here are my DNS settings

              Any idea / suggestion ?

              1 Reply Last reply Reply Quote 0
              • J Offline
                jaspras
                last edited by

                Uncheck

                Register DHCP leases in DNS forwarder
                Register DHCP static mappings in DNS forwarder

                get updates…

                check
                Register DHCP leases in DNS forwarder
                Register DHCP static mappings in DNS forwarder

                (P.S) i allways have these unchecked ...) but i dont know if its 100% OK

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