[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 11:45:08 -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=E6/WNuxMapgEOzCt2HungpWce0pcyD8N1vR8tnkjYmYMwbPeYIG4P4RBg0Zye9eCv+2/730IIRrkJ31yHAUHF5u6g3eBZL/QDkE0SLDXa9N4sh4GLoZ5aIRftcORH9VEy73zyXLxG9rIcqi6N8v1HjFUPINZGHTJlculQZIwPbk=
- 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=cSYu6Eehy12eDr9qGapanT1Rq6finZe8fquEu8x6FXMuG4aNQdkUIb9kLtuaHrE7kT6rC74JPR1UW+ImYarkTRqWUdcCgzwyd93bmj69l5y0eTEEdukToLX3zXY7aJ0fbRdPJ7oS781hMH0b3nM2vXf3f2Hl5Qi/zNzSIXhN0Y0=
- References: <29f517690709050643j7e7a1fden299061b755c0f834 (at) mail.gmail.com> <20070905151152.GA22073 (at) hswn.dk>
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.