per[513]: *fail: the anchor is NOT
ok and could not be fixed*
Oct 23 13:31:39 raspberrypi systemd[1]: Started Unbound DNS server.
If I then issue:
#> sudo systemctl restart unbound
#> sudo systemctl status unbound
Oct 23 13:48:30 raspberrypi systemd[1]: Starting Unbound DNS server...
Oct 23
erver...
> Oct 23 13:31:39 raspberrypi package-helper[513]: /var/lib/unbound/root.key
> has content
> Oct 23 13:31:39 raspberrypi package-helper[513]: *fail: the anchor is NOT
> ok and could not be fixed*
> Oct 23 13:31:39 raspberrypi systemd[1]: Started Unbound DNS server.
>
systemctl status unbound
Oct 23 13:31:38 raspberrypi systemd[1]: Starting Unbound DNS server...
Oct 23 13:31:39 raspberrypi package-helper[513]:
/var/lib/unbound/root.key has content
Oct 23 13:31:39 raspberrypi package-helper[513]: *fail: the anchor
is NOT ok and could not be fixed*
reboot, I get the following message when I run
> > #> sudo systemctl status unbound
> >
> > Oct 23 13:31:38 raspberrypi systemd[1]: Starting Unbound DNS
> server...
> > Oct 23 13:31:39 raspberrypi package-helper[513]:
> > /var/lib/unbound/root
I was not successful with the -R option. However, I was successful with making
the following change in raspi-config:
$ sudo raspi-config
-System Options
-Network at Boot
"Would you like boot to wait until a network connection is established?” Yes
I’m sure it’s probably not the best solution, bu