From owner-freebsd-stable Tue Apr 3 7:14:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sgi04-e.std.com (sgi04-e.std.com [199.172.62.134]) by hub.freebsd.org (Postfix) with ESMTP id ABB5637B71D for ; Tue, 3 Apr 2001 07:14:48 -0700 (PDT) (envelope-from kwc@world.std.com) Received: from world.std.com (world-f.std.com [199.172.62.5]) by sgi04-e.std.com (8.9.3/8.9.3) with ESMTP id KAA29294554; Tue, 3 Apr 2001 10:14:46 -0400 (EDT) Received: (from kwc@localhost) by world.std.com (8.9.3/8.9.3) id KAA13159; Tue, 3 Apr 2001 10:14:45 -0400 (EDT) Date: Tue, 3 Apr 2001 10:14:45 -0400 (EDT) From: Kenneth W Cochran Message-Id: <200104031414.KAA13159@world.std.com> To: "Brandon S. Allbery KF8NH" Subject: Re: Strange localhost NS look attempts Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From allbery@ece.cmu.edu Tue Apr 3 10:04:20 2001 >Date: Tue, 03 Apr 2001 10:04:03 -0400 >From: "Brandon S. Allbery KF8NH" >To: Kenneth W Cochran , Dan Larsson >cc: freebsd-stable@FreeBSD.ORG >Subject: Re: Strange localhost NS look attempts > >On Tuesday, April 03, 2001 09:55:53 AM -0400, Kenneth W Cochran > wrote: >+----- >| So, why should that be an invalid connection attempt? >| Looks to me like localhost should always be allowed to >| connect to itself... (?) >+--->8 > >If we ignore the LOG_IN_VAIN red herring, what's really happening here is Are you saying LOG_IN_VAIN is not such a Good Thing? >that you are running a nameserver on localhost which is returning some kind >of response after the querant (netscape?) has timed out (and therefore Yes, I'll say Netscape. Seems, for example, to work just fine with Lynx (http://localhost in both cases). >closed its query socket). So the real question is, why is the nameserver >timing out? Agreed, I think it has more to do with the nameserver. But maybe Yet Another Netscape Problem? Any idea(s) as to a fix? Or should I Just Live With It? Thanks! -kc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message