From owner-freebsd-stable Thu Apr 4 18: 2:50 2002 Delivered-To: freebsd-stable@freebsd.org Received: from backup.af.speednet.com.au (afgate.speednet.com.au [203.57.65.244]) by hub.freebsd.org (Postfix) with ESMTP id 5960537B417 for ; Thu, 4 Apr 2002 18:02:44 -0800 (PST) Received: from backup.af.speednet.com.au (andyf@backup.af.speednet.com.au [172.22.2.4]) by backup.af.speednet.com.au (8.11.6/8.11.6) with ESMTP id g3522AK39889; Fri, 5 Apr 2002 12:02:12 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Fri, 5 Apr 2002 12:02:09 +1000 (EST) From: Andy Farkas X-X-Sender: To: Cc: , stable at FreeBSD Subject: Re: named connections "in vain" In-Reply-To: <200204032204.g33M4Ax56644@drugs.dv.isc.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 4 Apr 2002 Mark.Andrews@isc.org wrote: > > Apr 3 07:38:20 sheol /kernel: Connection attempt to UDP 192.168.16.2:2314 fr > > om 192.168.16.2:53 > > > > I can't figure out what named is trying to talk with. > > Named is replying to clients that have already given up waiting. > These are most probably SERVFAILs saying that the nameserver has > given up but they could also be late answers where the nameserver > has had to work through several dead servers. Named is replying to itself, not a client, ie. the host at 192.168.16.2 made a request to 192.168.16.2 which timed-out. > > The only theory I can > > come up with is that named is not waiting long enough for the forwarder to > > reply, and does the query itself. When the forwarder does [finally] reply, > > the connection has already been closed (either by named or ipf)? I think it has something to do with the resolver library having a short time-out value and named having a longer one. An application (say sendmail) will use the resolver library to make a query. The query goes to the nameserver listed in /etc/resolv.conf which happens to be the same server as the app is running on. The query has a short time-out - it fails because named hasn't answered yet - the app goes on. Later, named gets an answer and tries to reply to a nonexistant connection. Do you know if in fact there are separate time-out values for the resolver library and named? -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message