On 2019/10/07 12:30, Florian Obser wrote:
> On Mon, Oct 07, 2019 at 11:16:22AM +0100, Stuart Henderson wrote:
> > On 2019/10/07 09:53, Theo Buehler wrote:
> > > $ doas /usr/sbin/unbound-anchor -v
> > > /var/unbound/db/root.key has content
> > > [1570433629] libunbound[28321:0] fatal error: could
On Mon, Oct 07, 2019 at 11:16:22AM +0100, Stuart Henderson wrote:
> On 2019/10/07 09:53, Theo Buehler wrote:
> > $ doas /usr/sbin/unbound-anchor -v
> > /var/unbound/db/root.key has content
> > [1570433629] libunbound[28321:0] fatal error: could not open autotrust file
> > for writing,
On Mon, Oct 07, 2019 at 11:16:22AM +0100, Stuart Henderson wrote:
> On 2019/10/07 09:53, Theo Buehler wrote:
> > $ doas /usr/sbin/unbound-anchor -v
> > /var/unbound/db/root.key has content
> > [1570433629] libunbound[28321:0] fatal error: could not open autotrust file
> > for writing,
On 2019/10/07 09:53, Theo Buehler wrote:
> $ doas /usr/sbin/unbound-anchor -v
> /var/unbound/db/root.key has content
> [1570433629] libunbound[28321:0] fatal error: could not open autotrust file
> for writing, /var/unbound/db/root.key.28321-0-1966ee948e00: No such file or
> directory
>
> The
Found this in my daily mail:
unbound-an -U root ttyp5 0.02 secs Sun
Oct 6 21:57 (0:00:00.16)
Since I have
auto-trust-anchor-file: "/var/unbound/db/root.key"
in my /var/unbound/etc/unbound.conf, on starting unbound, the rc.d
script runs
