On Wed, Nov 28, 2012 at 02:42:34PM -0500, Robert Edmonds wrote:
> > I'm having similar problems with unbound lately. I don't know how long
> > unbound
> > was running, but it has only processed 51031 before I restarted it. There
> > has
> > been no network interruption as far as I can tell. Howe
Guus Sliepen wrote:
> I'm having similar problems with unbound lately. I don't know how long unbound
> was running, but it has only processed 51031 before I restarted it. There has
> been no network interruption as far as I can tell. However, what is very
> strange is this behaviour:
hi, guus:
wh
I'm having similar problems with unbound lately. I don't know how long unbound
was running, but it has only processed 51031 before I restarted it. There has
been no network interruption as far as I can tell. However, what is very
strange is this behaviour:
[guus@host]~>host another.host.example.or
On 01/27/2012 05:45 PM, Robert Edmonds wrote:
> do you recall any other specific versions that this happened on? there
> was a rare new upstream version update in lenny (from 1.0.2 to 1.4.6
> iirc), do you happen to remember if you saw it before 1.4.x?
Not really, but I saw the problem on various
Toni Müller wrote:
> On 01/27/2012 04:40 PM, Robert Edmonds wrote:
> > is it possible you temporarily lost internet connectivity immediately
> > before resolving stopped?
>
> thanks for the pointer & idea, but I'm unconvinced. That would mean that
> losing Internet connectivity on the order of sec
Hi Robert,
On 01/27/2012 04:40 PM, Robert Edmonds wrote:
> is it possible you temporarily lost internet connectivity immediately
> before resolving stopped?
thanks for the pointer & idea, but I'm unconvinced. That would mean that
losing Internet connectivity on the order of seconds would be suffi
Toni Mueller wrote:
> I'm running unbound and discover, that after some uptime in the order of
> weeks, resolving stops. Unfortunately, I panicked and simply restarted
> the server to make it work again, so my means of diagnosing the problem
> are limited. Flushing a non-resolving zone didn't have
Package: unbound
Version: 1.4.14-2~bpo60+1
Severity: normal
Hi,
I'm running unbound and discover, that after some uptime in the order of
weeks, resolving stops. Unfortunately, I panicked and simply restarted
the server to make it work again, so my means of diagnosing the problem
are limited. Flu
8 matches
Mail list logo
