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

    BIND Package (or similar functioning authoritative DNS server)

    pfSense Packages
    19
    52
    17.9k
    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.
    • V
      voleatech
      last edited by

      Hi,

      sorry for the restart bug.
      That line of code changed because it was not working on ipv4 and ipv6 enabled bind systems.
      @wxop thank you for finding the fix.
      A new version was just submitted.

      Best
      Sven

      Voleatech
      pfSense Select Partner

      1 Reply Last reply Reply Quote 0
      • H
        helge000
        last edited by

        @wxop cheers!

        Was fighting over the same issue. I can reconfirm the extra space does the trick.

        1 Reply Last reply Reply Quote 0
        • W
          wxop
          last edited by

          @voleatech
          Thank for your amazing fast reaction, I just saw your PR at:
          https://github.com/pfsense/FreeBSD-ports/pull/193/files
          while I was myself just figuring on which GH branch I should post the fix to ;-)

          You definitely rock !!!!!!

          BTW, now that i found the bug (comparing this file with the squid.sh rcfile), I can not understand why this extra space character is needed even after re-reading the grep manual. As a reward for me having spent hours, to find/fix this bug, would someone be kind enough to explain me WHY the hell this fu***g space is mandatory  in the grep pattern ?
          best regards

          1 Reply Last reply Reply Quote 0
          • V
            voleatech
            last edited by

            @wxop
            Thanks :)

            the PR just got merged.

            I honestly don't know at this point why it didn't work.
            When I run it on the shell in pfSense both versions work on my box and output the PID.

            Best
            Sven

            Voleatech
            pfSense Select Partner

            1 Reply Last reply Reply Quote 0
            • W
              wxop
              last edited by

              @voleatech:

              the PR just got merged.

              Whaou !!! The Pf team is just as amazing as you… or I guess this is just a merge bot !  ;D

              I honestly don't know at this point why it didn't work. When I run it on the shell in pfSense both versions work on my box and output the PID.

              That's why it did take me hours to figure out why the "if/ps/grep/awk" statement was not working as expected… This is really weird!

              Any grep guru out there, to show us the light?

              all the best

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

                New version worked here as well! Thank you!!!

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

                  Now I can't get it to accept lookup requests on the WAN interface. Port scan shows port 53 is open as expected from internal interfaces, but port 53 is NOT open on the WAN interface.

                  Has this changed from previous versions or is my configuration messed up somewhere? It used to work on 2.2.6 with my existing configuration.

                  1 Reply Last reply Reply Quote 0
                  • V
                    voleatech
                    last edited by

                    @CaptainElmo

                    Bind didn't change except for the GUI between 2.2 and 2.3.
                    Can you check if bind is actually running on the WAN IP with netstat -ln?

                    Best
                    Sven

                    Voleatech
                    pfSense Select Partner

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

                      It turns out the problem was my WAN interface got messed up during the upgrade. I reassigned my WAN connection to a different interface and everything started working again.

                      I can't tell you how thrilled I am to have the BIND package available - thank you Sven!!!

                      1 Reply Last reply Reply Quote 0
                      • T
                        tdi
                        last edited by

                        Any chance of update to 9.10.4-P3 re: https://kb.isc.org/article/AA-01419/0 ?

                        1 Reply Last reply Reply Quote 0
                        • V
                          voleatech
                          last edited by

                          Hi,

                          the source for the bind package comes from the freeBSD port git repository.
                          You would have to ask in the freeBSD mailing list when this is going to be updated there.

                          Best
                          Sven

                          Voleatech
                          pfSense Select Partner
                          www.voleatech.de

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