From owner-freebsd-security  Wed Jun 16  4:41:56 1999
Delivered-To: freebsd-security@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id 0ECF414BD5
	for <security@FreeBSD.ORG>; Wed, 16 Jun 1999 04:41:52 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id NAA10264;
	Wed, 16 Jun 1999 13:41:40 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: junkmale@xtra.co.nz
Cc: security@FreeBSD.ORG, Dag-Erling Smorgrav <des@flood.ping.uio.no>
Subject: Re: named timeouts 
In-reply-to: Your message of "Wed, 16 Jun 1999 23:27:43 +1200."
             <19990616113019.HOKO311284.mta2-rme@wocker> 
Date: Wed, 16 Jun 1999 13:41:40 +0200
Message-ID: <10262.929533300@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

In message <19990616113019.HOKO311284.mta2-rme@wocker>, "Dan Langille" writes:
>On 16 Jun 99, at 13:17, Poul-Henning Kamp wrote:

>> Actually it doesnt, it means that the client closed his socket before
>> named got to answer...
>
>OK.  Now we're back to my initial theory.  How do I increase the time the 
>client keeps the socket open?  Or is that something possible to configure?

My guess is that the following happens:


	Client				Named

	create socket

	send request------------------->
					search through the
					entire world for 	
					answer, this takes
	send request------------------->quite some time,
					in fact very long
					time before we
					find the answer and
	receive answer<---------------- respond
	close socket
					handle next request
					(from cache)
	log_in_vain...<---------------- respond
	
--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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