Date: Tue, 3 Apr 2001 10:14:45 -0400 (EDT) From: Kenneth W Cochran <kwc@world.std.com> To: "Brandon S. Allbery KF8NH" <allbery@ece.cmu.edu> Cc: freebsd-stable@freebsd.org Subject: Re: Strange localhost NS look attempts Message-ID: <200104031414.KAA13159@world.std.com>
next in thread | raw e-mail | index | archive | help
>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" <allbery@ece.cmu.edu> >To: Kenneth W Cochran <kwc@world.std.com>, Dan Larsson <dl@tyfon.net> >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 ><kwc@world.std.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104031414.KAA13159>