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

    Unbound Restarting

    Scheduled Pinned Locked Moved DHCP and DNS
    10 Posts 5 Posters 5.5k 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.
    • L
      landossa
      last edited by

      Hello list,

      I am seeing unbnound restarts every second.  Any ideas what is causing this? Is this a bug?
      Name resolution is not an issue, just the restarts.

      Aug 30 10:49:22 	unbound 	23873:0 	notice: Restart of unbound 1.5.9.
      Aug 30 10:49:22 	unbound 	23873:0 	notice: init module 0: validator
      Aug 30 10:49:22 	unbound 	23873:0 	notice: init module 1: iterator
      Aug 30 10:49:23 	unbound 	23873:0 	info: start of service (unbound 1.5.9).
      Aug 30 10:49:23 	unbound 	23873:0 	info: service stopped (unbound 1.5.9).
      Aug 30 10:49:23 	unbound 	23873:0 	info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
      Aug 30 10:49:23 	unbound 	23873:0 	info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
      Aug 30 10:49:23 	unbound 	23873:0 	info: server stats for thread 1: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
      Aug 30 10:49:23 	unbound 	23873:0 	info: server stats for thread 1: requestlist max 0 avg 0 exceeded 0 jostled 0
      Aug 30 10:49:23 	unbound 	23873:0 	info: server stats for thread 2: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
      Aug 30 10:49:23 	unbound 	23873:0 	info: server stats for thread 2: requestlist max 0 avg 0 exceeded 0 jostled 0
      Aug 30 10:49:23 	unbound 	23873:0 	info: server stats for thread 3: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
      Aug 30 10:49:23 	unbound 	23873:0 	info: server stats for thread 3: requestlist max 0 avg 0 exceeded 0 jostled 0
      Aug 30 10:49:23 	unbound 	23873:0 	notice: Restart of unbound 1.5.9.
      Aug 30 10:49:23 	unbound 	23873:0 	notice: init module 0: validator
      Aug 30 10:49:23 	unbound 	23873:0 	notice: init module 1: iterator
      Aug 30 10:49:23 	unbound 	23873:0 	info: start of service (unbound 1.5.9). 
      

      thanks,
      Ll

      1 Reply Last reply Reply Quote 0
      • RonpfSR
        RonpfS
        last edited by

        Look at the DHCP log.

        2.4.5-RELEASE-p1 (amd64)
        Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
        Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

        1 Reply Last reply Reply Quote 0
        • L
          landossa
          last edited by

          Yeah I see a whole lot of these:

          
          Aug 30 11:36:24 	dhcpleases 		Sending HUP signal to dns daemon(58635)
          Aug 30 11:36:24 	dhcpleases 		Sending HUP signal to dns daemon(58635) 
          

          What is going on there?

          1 Reply Last reply Reply Quote 0
          • RonpfSR
            RonpfS
            last edited by

            When an new lease is issued, it will update unbound with it's entry if you have enabled Register DHCP leases in the DNS Resolver.

            2.4.5-RELEASE-p1 (amd64)
            Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
            Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

            1 Reply Last reply Reply Quote 0
            • L
              landossa
              last edited by

              I see. That appears to have stopped the logging. Is it right that the service restarts every time the DHCP host name is registered in the DNS?
              Or is this something on the bug fix list?

              thanks.

              1 Reply Last reply Reply Quote 0
              • I
                Inq
                last edited by

                Known bug : https://redmine.pfsense.org/issues/5413
                No solution in sight unfortunately.

                The problem with making something idiot proof is that the world keeps making better idiots.

                T 1 Reply Last reply Reply Quote 0
                • RonpfSR
                  RonpfS
                  last edited by

                  @landossa:

                  I see. That appears to have stopped the logging. Is it right that the service restarts every time the DHCP host name is registered in the DNS?
                  Or is this something on the bug fix list?

                  thanks.

                  It might be possible that most users don't see it reload in the logs because there is an issue with unbound not logging after reboot.

                  I have to restart unbound on every reboot in order for it to log when it reloads during pfBlockerNG cron update.

                  2.4.5-RELEASE-p1 (amd64)
                  Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                  Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                  1 Reply Last reply Reply Quote 0
                  • L
                    landossa
                    last edited by

                    Unchecking Register DHCP leases in the DNS Resolver in the DHCP Server Settings appears to have resolved it.

                    1 Reply Last reply Reply Quote 0
                    • U
                      ulki
                      last edited by

                      Hi,

                      I'm running 2.3.2 amd64.

                      I have the same issue with UNBOUND restarting every few seconds, when I enable IPv6 on the LAN interface (Tracking interface = WAN).
                      Services / DHCPv6 Server & RA / DHCPv6 Server is disabled. RA Router mode is set to "Unmanaged". Router priority to "Normal".

                      When I'm disabling IPv6 on the LAN interface (just using IPv4) everything is fine.
                      DHCP IPv4 leases are configured not to be registered in DNS.

                      To me it seems that IPv6 is trying to register IPv6 addresses in DNS and is restarting UNBOUND with every registration. (like in IPv4 with DNS registration enabled)

                      Is there any way to disable this behaviour in IPv6?

                      PS: Just tried DNS Forwarder instead of DNS Resolver (UNBOUND). DNS FOrwarder gets restarted by IPv6 (?) as well.

                      BR, Ulli.

                      1 Reply Last reply Reply Quote 1
                      • T
                        Traveler @Inq
                        last edited by

                        At the risk of necroposting, there is a merge request for this problem [1].

                        [1] https://github.com/pfsense/FreeBSD-ports/pull/751

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