https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292275
John Baldwin <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Works As Intended --- Comment #2 from John Baldwin <[email protected]> --- Having noticed the diff for `auto-trust-anchor` in the config file, I tried doing a manual `sh /etc/rc.d/local_unbound anchor` and then starting unbound and this allows local unbound to work again as a resolver. So the second failure appears to just be fallout from presumably some local changes I had to disable the auto-trust-anchor (in my internal VCS for this config it was commented out at the beginning) that were incompatible with the new default config. The original error from OpenSSL I am not sure of in terms of where it came from (the key/pem files are unchanged) or why rerunning the initial setup made it go away. Possibly the `setup` command for the rc.d script should also imply the `anchor` command (but I could see why maybe it would not). I did find it odd that `man unbound.conf` didn't work even though it shows up in `apropos` output (and is the name of the file), but only `man local-unbound.conf` works. Presumably that is so that `man unbound.conf` works for the version from ports. -- You are receiving this mail because: You are the assignee for the bug.
