unbound and ntp issuse

[Lowell Gilbert]

Slawa Olhovchenkov <slw at zxy.spb.ru> writes:

> Default install with local_unbound and ntpd can't be functional with
> incorrect date/time in BIOS:
>
> Unbound requred correct time for DNSSEC check and refuseing queries
> ("Jul 1 20:17:29 yellowrat unbound: [3444:0] info: failed to prime
> trust anchor -- DNSKEY rrset is not secure . DNSKEY IN")
>
> ntpd don't have any numeric IP of ntp servers in ntp.conf -- only
> symbolic names like 0.freebsd.pool.ntp.org, as result -- can't
> resolve (see above, about DNSKEY).

I can't see how this would happen. DNSSEC doesn't seem to be required in
a regular install as far as I can see. Certainly I don't have any
problem on any of my systems, and I've never configured an anchor on the
internal systems.

> IMHO, ntp.conf need to include some numeric IP of public ntp servers.

Ouch; that's a terrible idea, for several different reasons.