Unbound requires manual restart after upgrade

[jal]

I was running 2.3.2 for some years on an SG-4860 and finally decided to do a backup / clean install of 21.02.2 / restore to get caught up.

After 21.05 became available, I did the update via the GUI and all seemed to be well except I noticed that the appliance wasn't resolving DNS queries directed to it.

Checked the Status > Services page and Unbound was shown as running and no errors or warnings were seen in /var/log/resolver.log so I did a restart via the GUI and all was well.

Tonight I just did an upgrade from 21.05 -> 21.05.1 and had the same issue with Unbound not responding to queries (192.168.127.1 is the address of the SG-4860).

mrouter#ping vrf DMZ1 www.google.com
Translating "www.google.com"...domain server (192.168.127.1)
% Unrecognized host or address, or protocol not running.

Restarting the service cleared the issue.

mrouter#ping vrf DMZ1 www.google.com
Translating "www.google.com"...domain server (192.168.127.1) [OK]

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 142.250.190.68, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/30/48 ms

Not a huge issue now that I know to be on the lookout for it but I figured I should at least mention it here.

EDIT: For clarification, I posted here because I am not having any ongoing problems with Unbound once I restart it once following the upgrade so I figured this should be classified as upgrade-related.

[plfinch]

I suspect this is the same issue I reported here which has not been resolved as 21.05.1:

Every Reboot Requires Restart of DNS Resolver

Do a reboot and I bet you will need to follow it with an unbound restart to restore DNS resolution. Let us know…

Peter