These regular log, every 12 hours or so, lines are normal for unbound lines :
@jason001 said in New Update Package DNS problem:
Feb 5 07:39:54 unbound 48775 [48775:1] info: generate keytag query _ta-4f66. NULL IN
Feb 5 07:39:54 unbound 48775 [48775:0] info: generate keytag query _ta-4f66. NULL IN
Feb 5 19:22:11 unbound 48775 [48775:0] info: generate keytag query _ta-4f66. NULL IN
Feb 6 07:11:56 unbound 48775 [48775:0] info: generate keytag query _ta-4f66. NULL IN
Feb 6 18:13:22 unbound 48775 [48775:0] info: generate keytag query _ta-4f66. NULL IN
what they mean : the DNSSEC 'main' key is refreshed. See it as the hart beat of unbound.
I've the same thing ( reverse order ) :
fa207075-c832-4f58-bbc0-660508bdcfb1-image.png
When unbound is told to restart, you see this :
Feb 6 19:45:53 unbound 48775 [48775:0] info: service stopped (unbound 1.18.0).
and right after this line you see a lot of statistics (more or less useful) logged.
Keep in mind that pfSense never stops unbound, as this leaves the system without DNS.
pfSense always a stops it - then there is a 10 sec (or so) wait period, and then it starts it.
This sequence is a restart.
The admin could stop unbound, for whatever reason, using the GUI, for example by using this button :
bc31b106-b092-4457-8df8-781a52ebf8de-image.png
A reason might be : stop unbound, and set up dnsmasq, the forwarder, and use that one instead.
To inform pfSense that unbound shouldn't be (re)started anymore, during boot or at any time, you have to uncheck this option :
08ffc90e-ae56-4acf-95df-58a21f8ff320-image.png
and then set up the forwarder, dnsmasq :
2c956d3e-1389-4210-8d88-46b10314cc9a-image.png
So, your logs you've shown above don't show everything, as it ends while unbound was dumping statistics to the log.
It should be followed by a
2024-02-12 00:15:28.241637+01:00 unbound 51151 [51151:0] info: start of service (unbound 1.18.0).
if this - as shown :
e1150537-8f36-4143-821d-6eef1316848c-image.png
was really the end of the logs, nothing more was added, then something really bad has happened.
Like unbound process died on the spot. That's not normal at all.