Navigation

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

    DNS resolver Stop Working after upgrade 2.4.5 to 2.5.0

    DHCP and DNS
    6
    9
    299
    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.
    • M
      mohdikramsaif last edited by

      Dear Team,

      I have upgrade DNS resolver automatically Stop Working after upgrade 2.4.5 to 2.5.0. i have manually restart this service. Can you suggest.

      bingo600 A K 3 Replies Last reply Reply Quote 0
      • bingo600
        bingo600 @mohdikramsaif last edited by

        @mohdikramsaif

        See
        https://forum.netgate.com/topic/84312/unbound-segfaults-signal-11?_=1613798935997

        1 Reply Last reply Reply Quote 0
        • A
          Astronaut @mohdikramsaif last edited by

          @mohdikramsaif

          I have the same problem. DNS resolver stops after a few minutes.

          Logfile (after I restarted 3 times):

          Feb 20 10:11:56 dhcpleases 78457 Could not deliver signal HUP to process 74394: No such process.
          Feb 20 10:11:36 kernel pid 74394 (unbound), jid 0, uid 59: exited on signal 11
          Feb 20 10:07:44 dhcpleases 26574 Could not deliver signal HUP to process 81670: No such process.
          Feb 20 10:07:36 dhcpleases 34430 Could not deliver signal HUP to process 81670: No such process.
          Feb 20 10:06:36 kernel pid 81670 (unbound), jid 0, uid 59: exited on signal 11
          Feb 20 10:04:48 dhcpleases 34430 Could not deliver signal HUP to process 52649: No such process.
          Feb 20 10:04:36 dhcpleases 8162 Could not deliver signal HUP to process 52649: No such process.
          Feb 20 10:03:36 dhcpleases 8162 Could not deliver signal HUP to process 52649: No such process.
          Feb 20 10:02:50 kernel pid 52649 (unbound), jid 0, uid 59: exited on signal 11

          A 1 Reply Last reply Reply Quote 0
          • A
            Astronaut @Astronaut last edited by

            @astronaut

            Disabling "Register DHCP leases in the DNS Resolver" "solved" the problem.

            M A 2 Replies Last reply Reply Quote 0
            • M
              mohdikramsaif @Astronaut last edited by

              @astronaut Ok I will try this option. And update you after some time.
              Thanku so much.

              C 1 Reply Last reply Reply Quote 0
              • C
                CCNewb @mohdikramsaif last edited by

                @mohdikramsaif I had the same issue and the same solution as above works. Thanks for having me waste 30 minutes to figure it out. Surprised this blunder made it to a 'stable' release.

                1 Reply Last reply Reply Quote 0
                • A
                  Astronaut @Astronaut last edited by

                  @astronaut said in DNS resolver Stop Working after upgrade 2.4.5 to 2.5.0:

                  Disabling "Register DHCP leases in the DNS Resolver" "solved" the problem.

                  I ran it for about 18 hours with the setting disabled. No crashes. No trace of problems in the log file.

                  This morning I enabled "Register DHCP leases in the DNS Resolver" again. The router ran for abouter before the resolver crashed again. Thus the problem can be recreated at my end.

                  1 Reply Last reply Reply Quote 0
                  • K
                    khuynh @mohdikramsaif last edited by

                    @mohdikramsaif

                    Try upgrading Unbound to 1.13.1.
                    It helped me.

                    See this thread for details

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

                      I got a similar problem with VLANs. My primary vlan runs without any problems. But every morning I boot up a PC within a different VLAN it can't lookup domains. Nslookup ends with a Timeout. After restarting the dns resolver it works immediately.

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post

                      Products

                      • Platform Overview
                      • TNSR
                      • pfSense Plus
                      • Appliances

                      Services

                      • Training
                      • Professional Services

                      Support

                      • Subscription Plans
                      • Contact Support
                      • Product Lifecycle
                      • Documentation

                      News

                      • Media Coverage
                      • Press
                      • Events

                      Resources

                      • Blog
                      • FAQ
                      • Find a Partner
                      • Resource Library
                      • Security Information

                      Company

                      • About Us
                      • Careers
                      • Partners
                      • Contact Us
                      • Legal
                      Our Mission

                      We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

                      Subscribe to our Newsletter

                      Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

                      © 2021 Rubicon Communications, LLC | Privacy Policy