unbound and ntp issuse

[krad]

running this at boot time may help as well

unbound-control set_option  val-permissive-mode: yes

then after ntpd has started up run this

unbound-control set_option  val-permissive-mode: no

Yes work around's, but work around's work by definition.

On 7 June 2016 at 15:00, krad <kraduk at gmail.com> wrote:

> it's a non solvable problem though as its a deadlock. You have to remove
> one of the criteria in order to fix the issue automatically.
>
> On 7 June 2016 at 14:32, Slawa Olhovchenkov <slw at zxy.spb.ru> wrote:
>
>> On Tue, Jun 07, 2016 at 07:29:32AM -0600, Ian Lepore wrote:
>>
>> > On Tue, 2016-06-07 at 12:10 +0100, krad wrote:
>> > > whops that should be
>> > >
>> > > ntpdate_hosts not servers
>> > >
>> >
>> > These suggestions are essentially insane because they're ignoring the
>> > basic fact that the freebsd installer creates a non-working system.  If
>> > unbound requires DNSSEC, and DNSSEC requires good time, and good time
>> > requires hostname resolution, then that circular dependency is a
>> > problem that the freebsd project needs to fix, not something to be
>> > hacked around by each individual sysadmin.
>>
>> Exactly! This is may point!
>>
>> > It is a bit disturbing to me that the project members who created this
>> > situation have been silent in the face of *months* of reporting of it
>> > by several different users.
>>
>
>