Re: fail: the anchor is NOT ok and could not be fixed

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,

Re: fail: the anchor is NOT ok and could not be fixed

Thanks for the detailed explanation! Are you referring to this area: do_root_trust_anchor_update() { if $ROOT_TRUST_ANCHOR_UPDATE; then if [ -n "$ROOT_TRUST_ANCHOR_FILE" ]; then if [ -r "$DNS_ROOT_KEY_FILE" ]; then if [ ! -e "$ROOT_TRUST_ANCHOR_FILE" -o

Re: fail: the anchor is NOT ok and could not be fixed

On 27/10/2020 09:38, Gil Levy via Unbound-users wrote: Anyone? Still couldn't fix this on boot. Appreciate your help. On Fri, 23 Oct 2020 at 13:51, Gil Levy > wrote: After a system reboot, I get the following message when I run #> sudo systemctl status

Re: fail: the anchor is NOT ok and could not be fixed

Anyone? Still couldn't fix this on boot. Appreciate your help. On Fri, 23 Oct 2020 at 13:51, Gil Levy wrote: > After a system 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

fail: the anchor is NOT ok and could not be fixed

After a system 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.key has content Oct 23 13:31:39 raspberrypi