Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Aug 2017 23:54:14 +0200
From:      Datasmurf <datasmurf@mail.ru>
To:        freebsd-questions@freebsd.org
Cc:        byrnejb@harte-lyne.ca
Subject:   Re: FreeBSD-11 - local_unbound logging
Message-ID:  <20170817235414.a0eef6462b2ec2b2d3385884@mail.ru>
In-Reply-To: <7eeceea605f1c7e5d4a786822268e86d.squirrel@216.185.71.106>
References:  <d07d474ff8fa5689248708eaa62d506d.squirrel@webmail.harte-lyne.ca> <7eeceea605f1c7e5d4a786822268e86d.squirrel@216.185.71.106>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Thu, 17 Aug 2017 10:32:58 -0400
"James B. Byrne via freebsd-questions" <freebsd-questions@freebsd.org>
wrote:

[snip]
> 
> So what is going on?  If I have a configuration issue with DNSSEC or
> with Unbound then I really need to discover what it is and fix it. 
> Otherwise I am left with the unsettling alternative that there is a
> serious bug in unbound.
> 
> What is really bothering me is that restarting local_unbound makes the
> problem go away.  If this was a configuration issue then the problem
> should not disappear on a restart only to reoccur some time later.
> 

[snap]

Hello James,

i'm sure not an expert on unbound and dns/dnssec stuff. 
But on the Workstation on which unbound misbehaves could it be that
the system clock is not set correct? 
 

greetings

Daniel

-- 
#irc - real netizens last resort



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20170817235414.a0eef6462b2ec2b2d3385884>