Unbound need restart to log



  • Yesterday I updated from 2.3.1_p5 to 2.3.2.
    After the reboot, unbound doesn't log much in Status/System Logs/System/DNS Resolver

    I have to go to Status/Services and restart the DNS Resolver in order to get it to log.

    The issue is present since 2.1.x, as I don't reboot often it doesn't bother me to restart the service when needed.

    Jul 26 04:16:19 	unbound 	39301:0 	info: average recursion processing time 0.573138 sec
    Jul 26 04:16:19 	unbound 	39301:0 	info: server stats for thread 0: requestlist max 8 avg 2.03704 exceeded 0 jostled 0
    Jul 26 04:16:19 	unbound 	39301:0 	info: server stats for thread 0: 104 queries, 50 answers from cache, 54 recursions, 0 prefetch
    Jul 26 04:16:17 	unbound 	39301:0 	info: service stopped (unbound 1.5.9).
    Jul 26 04:03:04 	unbound 	39301:0 	info: start of service (unbound 1.5.9).
    Jul 26 04:03:03 	unbound 	39301:0 	notice: init module 1: iterator
    Jul 26 04:03:03 	unbound 	39301:0 	notice: init module 0: validator
    Jul 25 21:55:48 	unbound 	25303:0 	info: start of service (unbound 1.5.9).
    Jul 25 21:55:48 	unbound 	25303:0 	notice: init module 1: iterator
    Jul 25 21:55:48 	unbound 	25303:0 	notice: init module 0: validator
    Jul 25 21:55:36 	kernel 		unbound: 1.5.8 -> 1.5.9 [pfSense]
    Jul 25 21:55:36 	kernel 		dnsmasq: 2.76,1 [pfSense]
    Jul 25 21:20:13 	unbound 	11825:0 	info: start of service (unbound 1.5.8). 
    


  • I have been monitoring reboots in the last month and I can confirm that on reboot, DNS resolver doesn't log reloads to Status / System Logs /System / DNS Resolver.
    pfBlockerNG DNSBL reloads unbound at each cron, but nothing shows in the DNS Resolver Logs

    After restarting the unbound service in Status / Services, unbound will log reload messages until next reboot.

    presently using```
    2.3.3-DEVELOPMENT (i386)
    built on Tue Aug 09 12:18:21 CDT 2016
    FreeBSD 10.3-RELEASE-p6



  • Does anyone maintain unbound ?


Log in to reply