From owner-freebsd-security Wed Jun 16 12:23: 5 1999 Delivered-To: freebsd-security@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id EBA8214F39 for ; Wed, 16 Jun 1999 12:22:57 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA51664; Wed, 16 Jun 1999 13:22:38 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA01067; Wed, 16 Jun 1999 13:22:39 -0600 (MDT) Message-Id: <199906161922.NAA01067@harmony.village.org> To: Poul-Henning Kamp Subject: Re: named timeouts Cc: dan.langille@dvl-software.com, Dag-Erling Smorgrav , security@FreeBSD.ORG, Mike Nowlin In-reply-to: Your message of "Wed, 16 Jun 1999 13:17:01 +0200." <10181.929531821@critter.freebsd.dk> References: <10181.929531821@critter.freebsd.dk> Date: Wed, 16 Jun 1999 13:22:39 -0600 From: Warner Losh Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <10181.929531821@critter.freebsd.dk> Poul-Henning Kamp writes: : Actually it doesnt, it means that the client closed his socket before : named got to answer... Yes. These messages have nothing to do with the name SERVER, but rather the name CLIENT. I get them on the machine I'm typing on all the time (10-30 per day) and it isn't even running a name server. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message