From owner-freebsd-stable  Thu Jan 18 16: 7: 0 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135])
	by hub.freebsd.org (Postfix) with ESMTP id 12E9E37B402
	for <stable@FreeBSD.ORG>; Thu, 18 Jan 2001 16:06:32 -0800 (PST)
Received: (from dillon@localhost)
	by earth.backplane.com (8.11.1/8.9.3) id f0J064Y87542;
	Thu, 18 Jan 2001 16:06:04 -0800 (PST)
	(envelope-from dillon)
Date: Thu, 18 Jan 2001 16:06:04 -0800 (PST)
From: Matt Dillon <dillon@earth.backplane.com>
Message-Id: <200101190006.f0J064Y87542@earth.backplane.com>
To: Gregory Bond <gnb@itga.com.au>
Cc: Mark.Andrews@nominum.com, Mike Tancsa <mike@sentex.net>,
	Christopher Schulte <christopher@schulte.org>, stable@FreeBSD.ORG
Subject: Re: Weird sporadic DNS resolution problems 
References:  <200101182350.KAA17112@lightning.itga.com.au>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


:
:> 	This is a *human* problem not a software problem.
:
:I don't think so.  I've investigated cases where the MX record is fine, the
:name servers are all responding with AA, but sendmail still refuses to deliver
:the mail.  I suspect some sort of negative caching but I can't work out where.

    This is the only caching sendmail does:

    # persistent host status directory
    #O HostStatusDirectory=.hoststat

    Sendmail also stores stores the last error in the spool file, and you
    can give it the MinQueueAge option:

    # minimum time in queue before retry
    #O MinQueueAge=30m 

    To cause it to skip a failed queue file for X minutes before trying 
    again.  This prevents a single queue file from stalling all of the 
    sendmail's running the queue.

    That's it.  Sendmail doesn't cache anything else between connection
    attempts.

						-Matt




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message