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

    Unbound frequently restarts on 2.2 - is this normal?

    DHCP and DNS
    17
    43
    9.4k
    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.
    • K
      kejianshi
      last edited by

      It would be interesting and probably helpful to see your DHCP server setting and your unbound settings.

      1 Reply Last reply Reply Quote 0
      • M
        macboy6
        last edited by

        Ok, this issue was definitely caused by a misconfiguration on my Apple TV (connected to both wired and wireless simultaneously).  This was causing the Apple TV to get stuck in a DHCP request loop (verified by DHCP logs).

        In addition, I have the following setting in Unbound: Register DHCP leases in the DNS Resolver

        Since I corrected the Apple TV issue, the hourly unbound restarts have stopped.

        Thanks,
        Marco

        1 Reply Last reply Reply Quote 0
        • K
          kejianshi
          last edited by

          Sounds like something I see lots of people doing with laptops.  Plugging in wired while wireless is still on.  Same with IP Cams.

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

            @Inq:

            One thing is clear in my case : Every time the dhcp service writes leases to leases file the unbound service restarts…every single time.

            I noticed the same thing the other day, unbound restarting every time the dhcp service wrote the leases file, about once an hour.  It hadn't been doing this until I changed the setting for "unwanted reply threshold" in the dns resolver advanced settings from disabled to 10 million.  I changed it back to disabled yesterday and unbound has not restarted since.  No idea what the relationship is, but there seems to be one.

            edit: nevermind, changed another setting in dns resolver and now unbound is restarting at the same time the dhcp service writes the leases file again…

            1 Reply Last reply Reply Quote 0
            • K
              kevindd992002
              last edited by

              I'm experiencing the same problem with Unbound. Does this mean that it's normal for it to restart if the option to "Register DHCP leases in the DNS Resolver" is enabled?

              1 Reply Last reply Reply Quote 0
              • GertjanG
                Gertjan
                last edited by

                @wbond:

                edit: nevermind, changed another setting in dns resolver and now unbound is restarting at the same time the dhcp service writes the leases file again…

                I see the same thing: Unbound is restarting on every DHCPREQUEST - DHCPACK  sequence:
                Status: System logs: DHCP log:

                04-06-2015	09:49:36	Local7.Info	192.168.1.1	Apr  6 09:49:37 dhcpd: DHCPREQUEST for 192.168.2.235 from 78:3a:84:xx:34:1f (Philippes-Air) via sis0
04-06-2015	09:49:36	Local7.Info	192.168.1.1	Apr  6 09:49:37 dhcpd: DHCPACK on 192.168.2.235 to 78:3a:84:xx:34:1f (Philippes-Air) via sis0
04-06-2015	09:49:36	User.Info	192.168.1.1	Apr  6 09:49:37 dhcpleases: Sending HUP signal to dns daemon(53865)

                I guess, when "Sending HUP signal to dns daemon" is fired, Unbound restarts.
                At that moment, on the "Status: System logs: Resolver", I see (reversed time order):

                04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info: start of service (unbound 1.5.3).
04-06-2015	09:52:08	Daemon.Notice	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] notice: init module 0: iterator
04-06-2015	09:52:08	Daemon.Notice	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] notice: Restart of unbound 1.5.3.
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info:    0.524288    1.000000 1
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info:    0.262144    0.524288 2
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info:    0.131072    0.262144 1
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info: lower(secs) upper(secs) recursions
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info: [25%]=0.262144 median[50%]=0.393216 [75%]=0.524288
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info: histogram of recursion processing times
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info: average recursion processing time 0.414164 sec
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info: server stats for thread 1: requestlist max 4 avg 1 exceeded 0 jostled 0
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info: server stats for thread 1: 4 queries, 0 answers from cache, 4 recursions, 0 prefetch
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info:    0.524288    1.000000 4
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info:    0.262144    0.524288 5
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info:    0.131072    0.262144 3
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info:    0.065536    0.131072 3
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info:    0.032768    0.065536 3
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info:    0.016384    0.032768 1
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info: lower(secs) upper(secs) recursions
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info: [25%]=0.08192 median[50%]=0.240299 [75%]=0.484966
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info: histogram of recursion processing times
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info: average recursion processing time 0.331678 sec
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info: server stats for thread 0: requestlist max 28 avg 3.36842 exceeded 0 jostled 0
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info: server stats for thread 0: 25 queries, 6 answers from cache, 19 recursions, 0 prefetch
04-06-2015	09:52:08	Daemon.Info	192.168.1.1	Apr  6 09:52:09 unbound: [53865:0] info: service stopped (unbound 1.5.3).

                This means that unbound restart several times per minute … is this normal ???
                Or is this what it is all about, the setting "DHCP Registration" on the "Services: DNS Resolver" page ?

                No "help me" PM's please. Use the forum, the community will thank you.
                Edit : and where are the logs ??

                1 Reply Last reply Reply Quote 0
                • D
                  doktornotor Banned
                  last edited by

                  @Gertjan:

                  Or is this what it is all about, the setting "DHCP Registration" on the "Services: DNS Resolver" page ?
                  This means that unbound restart several times per minute … is this normal ???

                  No, it's not normal. And in general, the "wheeeeeeeee something might have changed (99% of cases absolutely nothing at all changed and apinger just went haywire as usual) so lets restart all services and packages" mentality that pfSense has grown is an absolute disaster. (Recently, someone finally nuked this nonsense on routing packages like OpenBGPD/Quagga where it was making them just completely no-op.)

                  Example of this madness: https://redmine.pfsense.org/issues/4474

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

                    I upgraded to 2.2.1 and this is still occurring very frequently for me.

                    
Apr 7 18:46:45	unbound: [53511:0] info: start of service (unbound 1.5.3).
Apr 7 18:46:45	unbound: [53511:0] info: service stopped (unbound 1.5.3).
Apr 7 18:36:50	unbound: [53511:0] info: start of service (unbound 1.5.3).
Apr 7 18:36:50	unbound: [53511:0] info: service stopped (unbound 1.5.3).
Apr 7 18:31:39	unbound: [53511:0] info: start of service (unbound 1.5.3).
Apr 7 18:31:39	unbound: [53511:0] info: service stopped (unbound 1.5.3).
Apr 7 18:26:56	unbound: [53511:0] info: start of service (unbound 1.5.3).
Apr 7 18:26:56	unbound: [53511:0] info: service stopped (unbound 1.5.3).
Apr 7 18:21:31	unbound: [53511:0] info: start of service (unbound 1.5.3).
Apr 7 18:21:31	unbound: [53511:0] info: service stopped (unbound 1.5.3).
Apr 7 18:17:00	unbound: [53511:0] info: start of service (unbound 1.5.3).
Apr 7 18:17:00	unbound: [53511:0] info: service stopped (unbound 1.5.3).
Apr 7 18:10:10	unbound: [53511:0] info: start of service (unbound 1.5.3).
Apr 7 18:10:09	unbound: [53511:0] info: service stopped (unbound 1.5.3).
Apr 7 18:09:23	unbound: [53511:0] info: start of service (unbound 1.5.3).
Apr 7 18:09:23	unbound: [53511:0] info: service stopped (unbound 1.5.3).
                    1 Reply Last reply Reply Quote 0
                    • B
                      Barnabas
                      last edited by

                      I have been having this problem also.
                      I first thought it was BandwidthD, but I removed and did not help.

                      Apr 11 18:03:42 	unbound: [76411:0] info: service stopped (unbound 1.5.3).
Apr 11 18:03:42 	unbound: [76411:0] info: server stats for thread 0: 228 queries, 48 answers from cache, 180 recursions, 0 prefetch
Apr 11 18:03:42 	unbound: [76411:0] info: server stats for thread 0: requestlist max 20 avg 2.90556 exceeded 0 jostled 0
Apr 11 18:03:42 	unbound: [76411:0] info: average recursion processing time 0.291716 sec
Apr 11 18:03:42 	unbound: [76411:0] info: histogram of recursion processing times
Apr 11 18:03:42 	unbound: [76411:0] info: [25%]=0.107241 median[50%]=0.236444 [75%]=0.40778
Apr 11 18:03:42 	unbound: [76411:0] info: lower(secs) upper(secs) recursions
Apr 11 18:03:42 	unbound: [76411:0] info: 0.000000 0.000001 2
Apr 11 18:03:42 	unbound: [76411:0] info: 0.008192 0.016384 10
Apr 11 18:03:42 	unbound: [76411:0] info: 0.016384 0.032768 13
Apr 11 18:03:42 	unbound: [76411:0] info: 0.032768 0.065536 13
Apr 11 18:03:42 	unbound: [76411:0] info: 0.065536 0.131072 11
Apr 11 18:03:42 	unbound: [76411:0] info: 0.131072 0.262144 51
Apr 11 18:03:42 	unbound: [76411:0] info: 0.262144 0.524288 63
Apr 11 18:03:42 	unbound: [76411:0] info: 0.524288 1.000000 10
Apr 11 18:03:42 	unbound: [76411:0] info: 1.000000 2.000000 6
Apr 11 18:03:42 	unbound: [76411:0] info: 2.000000 4.000000 1
Apr 11 18:03:42 	unbound: [76411:0] notice: Restart of unbound 1.5.3.
Apr 11 18:03:42 	unbound: [76411:0] notice: init module 0: validator
Apr 11 18:03:42 	unbound: [76411:0] notice: init module 1: iterator
Apr 11 18:03:42 	unbound: [76411:0] info: start of service (unbound 1.5.3).
Apr 11 18:07:39 	unbound: [76411:0] info: service stopped (unbound 1.5.3).
Apr 11 18:07:39 	unbound: [76411:0] info: server stats for thread 0: 36 queries, 4 answers from cache, 32 recursions, 0 prefetch
Apr 11 18:07:39 	unbound: [76411:0] info: server stats for thread 0: requestlist max 14 avg 3.96875 exceeded 0 jostled 0
Apr 11 18:07:39 	unbound: [76411:0] info: average recursion processing time 0.224321 sec
Apr 11 18:07:39 	unbound: [76411:0] info: histogram of recursion processing times
Apr 11 18:07:39 	unbound: [76411:0] info: [25%]=0.104858 median[50%]=0.191567 [75%]=0.299593
Apr 11 18:07:39 	unbound: [76411:0] info: lower(secs) upper(secs) recursions
Apr 11 18:07:39 	unbound: [76411:0] info: 0.008192 0.016384 1
Apr 11 18:07:39 	unbound: [76411:0] info: 0.016384 0.032768 2
Apr 11 18:07:39 	unbound: [76411:0] info: 0.032768 0.065536 2
Apr 11 18:07:39 	unbound: [76411:0] info: 0.065536 0.131072 5
Apr 11 18:07:39 	unbound: [76411:0] info: 0.131072 0.262144 13
Apr 11 18:07:39 	unbound: [76411:0] info: 0.262144 0.524288 7
Apr 11 18:07:39 	unbound: [76411:0] info: 0.524288 1.000000 1
Apr 11 18:07:39 	unbound: [76411:0] info: 1.000000 2.000000 1
Apr 11 18:07:39 	unbound: [76411:0] notice: Restart of unbound 1.5.3.
Apr 11 18:07:39 	unbound: [76411:0] notice: init module 0: validator
Apr 11 18:07:39 	unbound: [76411:0] notice: init module 1: iterator
Apr 11 18:07:39 	unbound: [76411:0] info: start of service (unbound 1.5.3).

                      Any clues?

                      1 Reply Last reply Reply Quote 0
                      • B
                        Barnabas
                        last edited by

                        I am also getting this in my system log

                        Apr 11 19:19:52 	php-fpm[2552]: /services_unbound.php: The command '/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid bge0' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.2.6 Copyright 2004-2014 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Wrote 0 deleted host decls to leases file. Wrote 0 new dynamic host decls to leases file. Wrote 12 leases to leases file. Listening on BPF/bge0/00:14:22:db:b4:a9/10.8.8.0/24 Sending on BPF/bge0/00:14:22:db:b4:a9/10.8.8.0/24 Can't bind to dhcp address: Address already in use Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If yo

                        DHCP doesn't like something…

                        1 Reply Last reply Reply Quote 0
                        • K
                          kevindd992002
                          last edited by

                          Any solution to this?

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

                            Is this a confirmed bug? If so, how can we report it? I'm having the same issue.

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

                              Hi,

                              I have the same issue. I use pfsense 2.2.1 and DNS Resolver in forwarding mode. DNSSEC is on, and I've set DHCP leases/mappings to be registered.

                              It is very flaky, as it often claims it cannot resolve hosts which are clearly available to others. And then the restarts multiple times per day (sometimes multiple times per hour)…. not good!

                              Anything I can do/try?

                              Thanks!

                              1 Reply Last reply Reply Quote 0
                              • GertjanG
                                Gertjan
                                last edited by

                                Think about it like this:
                                Every time a new lease is being registered on the DHCP server, it updates its lease-file - and if unbound is running, it also write to this file: /var/unbound/dhcpleases_entries.conf.
                                "unbound" should read this DHCP lease file to update its own internal records.
                                pfSense restarts the "unbound" service ( /etc/inc/unbound.inc: line 676: unbound_control("reload"); whenever a new DHCP lease is issued. This is normal and "by actual design".

                                The thing is : by default, unbound is noisy in the log when it 'restarts'. So switch to less log details : Goto Services: DNS Resolver: Advanced - look for "Log level verbosity" and set it to "level 0".

                                Idea: what about a bigger DHCP lease times ? That will lower the unboud-restart activity.

                                No "help me" PM's please. Use the forum, the community will thank you.
                                Edit : and where are the logs ??

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

                                  @Gertjan:

                                  Think about it like this:
                                  […] whenever a new DHCP lease is issued. This is normal and "by actual design".

                                  The thing is : by default, unbound is noisy in the log when it 'restarts'. So switch to less log details : Goto Services: DNS Resolver: Advanced - look for "Log level verbosity" and set it to "level 0".

                                  Idea: what about a bigger DHCP lease times ? That will lower the unboud-restart activity.

                                  Then "by actual design" means bad design.

                                  Setting to "level 0" removes the log entries, but not the problem.

                                  The fact of the matter is that DNS Resolver restarts ALL THE TIME on my network with quite a few LAN devices and after each restart there's a few seconds where DNS queries are not resolved.

                                  This is horrible and makes resolver useless for us.

                                  Please fix.

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    doktornotor Banned
                                    last edited by

                                    Errr… reload (SIGHUP) should re-read the configuration and not disrupt service (service stopped). Definitely not sure the last couple of posts is discussing the same issue.

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

                                      @doktornotor:

                                      Errr… reload (SIGHUP) should re-read the configuration and not disrupt service (service stopped). Definitely not sure the last couple of posts is discussing the same issue.

                                      Beats me. My point is that DNS Resolver has a substantial problem that needs to be fixed.

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

                                        @waingro:

                                        Beats me.

                                        ? Tried 2.2.2. ?

                                        1 Reply Last reply Reply Quote 0
                                        • GertjanG
                                          Gertjan
                                          last edited by

                                          @doktornotor:

                                          Errr… reload (SIGHUP) should re-read the configuration and not disrupt service (service stopped).

                                          Check out for yourself:
                                          /etc/inc/unbound.inc: last function : https://github.com/pfsense/pfsense/blob/master/etc/inc/unbound.inc#L706
                                          This one gets called every time the system hosts file get rewritten. (here: /var/etc/hosts)
                                          In this file (hosts) are all DHCP leases - and its always up to date.
                                          So, a lot of DHCP activity means : ….. unbound gets "unbound-control reload" (here https://github.com/pfsense/pfsense/blob/master/etc/inc/unbound.inc#L468 )

                                          @doktornotor:

                                          Definitely not sure the last couple of posts is discussing the same issue.

                                          I guess it is: I saw many many "reload" lines.
                                          For me its was a stupid Windows 7 PC (one out of a serie of 6 PC bought, installed, setup identical) that renewed its DHCP lease every 5 (yes: 5 minutes) so …. I ditched the PC for the moment, the DHCP storm stopped, the frequent (as said, every 5 minutes) unbound reloading like a chain-gun stopped.

                                          Right now, it reload about 40 times a day (I have Cpative portal visitors):

                                          Apr 22 23:20:41 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 23:20:41 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 22:19:25 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 22:19:25 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 21:18:47 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 21:18:47 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 20:18:46 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 20:18:46 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 19:18:20 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 19:18:20 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 18:17:45 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 18:17:45 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 17:16:25 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 17:16:25 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 16:15:58 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 16:15:58 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 15:01:26 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 15:01:26 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 13:34:37 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 13:34:37 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 12:29:24 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 12:29:24 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 10:22:12 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 10:22:12 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 09:19:33 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 09:19:33 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 08:11:30 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 08:11:30 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 07:09:08 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 07:09:08 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 06:05:15 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 06:05:15 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 05:03:25 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 05:03:25 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 03:55:15 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 03:55:15 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 02:55:14 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 02:55:14 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 01:53:57 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 01:53:57 unbound: [68253:0] info: service stopped (unbound 1.5.3).
                                          Apr 22 00:50:59 unbound: [68253:0] info: start of service (unbound 1.5.3).
                                          Apr 22 00:50:59 unbound: [68253:0] info: service stopped (unbound 1.5.3).

                                          I didn't have a look at the unbound source code (yet) but ""unbound-control reload" means to me : restart it.
                                          All this to force it to reread the hosts file (and dhcp leases file ?).
                                          I don't think its a bug, neither saying it wrong - maybe unbound could be informed otherwise to have it read some files again … maybe not .... let the coder decide ;)

                                          Reloading happens when I see this in the DHCP log:

                                          Apr 22 23:20:41 dhcpd: Wrote 250 leases to leases file.
                                          Apr 22 23:20:41 dhcpd: Wrote 0 new dynamic host decls to leases file.
                                          Apr 22 23:20:41 dhcpd: Wrote 0 deleted host decls to leases file.

                                          That's why I was thinking that it is DHCP-activity related. (and thus, /var/etc/hosts file related)

                                          I could be wrong, of course :)

                                          No "help me" PM's please. Use the forum, the community will thank you.
                                          Edit : and where are the logs ??

                                          1 Reply Last reply Reply Quote 0
                                          • P
                                            phil.davis
                                            last edited by

                                            I imagine/hope/think that "reload" causes the running unbound to simply re-read its config (which includes reading associated leases or whatever other stuff is pointed to by the config) and internally implement that on-the-fly without any significant interruption of user service.

                                            But maybe that is not the case! Someone could look in the unbound source code and see how a "reload" message really is processed.

                                            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                                            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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