[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] Stupid sound question - "DNS Error"
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] Stupid sound question - "DNS Error"
- From: "Gary Baluha" <gumby3203 (at) gmail.com>
- Date: Wed, 5 Sep 2007 13:15:50 -0400
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=FjOFrhAYkJA7fIkG6wF5K5IDJtDr81QQI7akB7XXKdjru1EYaR5E5SFc2ka1IyOx/QWCVFxxoxP2FApre87ZKOLfYTjB3umn4vPy8cG8iMPzWgK4TG21hOPdu9l8fjRjE6iQMwswtXXU3jG1vuL/iMHNbC+uiNNo5RDUze4x9gc=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=ND4IhzD+l5STeAUSd3GFpGTHcnDpACeAsN1aofrfN7/PY14VTQG/Xt+Xh5EWr9pXWnhTxOu6JdQmy9YAUHn3IgNvUGvmvOG1TabRuLf6xVBpLBlLAvP7QySWO5zLDr3+0ddsSptlFhQxGvKLD+w6qkZeCQMSPf7kzX4yZowfC8A=
- References: <29f517690709050643j7e7a1fden299061b755c0f834 (at) mail.gmail.com> <20070905151152.GA22073 (at) hswn.dk> <29f517690709050845u39887165p894beec3aeca431d (at) mail.gmail.com>
It seems adding a local caching DNS server did no fix this problem. I'm
truely at a loss now, because nothing I test manually seems to indicate a
problem. Also, when the hobbit alerts go red due to "DNS Error", as soon as
I go to check, it has cleared up already.
On 9/5/07, Gary Baluha <gumby3203 (at) gmail.com> wrote:
>
> On 9/5/07, Henrik Stoerner <henrik (at) hswn.dk> wrote:
> >
> > On Wed, Sep 05, 2007 at 09:43:32AM -0400, Gary Baluha wrote:
> > > It sounds like an obvious answer, but what does the http/https
> > monitoring
> > > error "DNS Error" mean, exactly?
> >
> > It means Hobbit could not lookup the hostname in DNS.
>
>
> Okay, I thought it was pretty self explanatory, but a quick glance at the
> code wasn't obvious to me.
>
> > Specifically, I have several https checks defined in Hobbit, and a good
> > > number of them get the "DNS Error" message multiple times a day;
> > roughly on
> > > the order of every 1-3 hours. I have manually verified that DNS is
> > working
> > > for these hosts. It might help me troubleshoot this if I know exactly
> > how
> > > Hobbit comes to this determination, and if anything else other than
> > DNS
> > > could cause it to appear.
> >
> > A local caching DNS server is usually a good idea. Hobbit has been known
> >
> > to knock out DNS servers, because it sends a lot of requests very
> > quickly.
>
>
> Well, two suggestions to have a local caching DNS must mean it's a pretty
> good idea. I set this up, and will see if that fixes the problem.
>
>
>