Date: Wed, 9 Apr 1997 18:49:42 -0400 (EDT) From: Bradley Dunn <bradley@dunn.org> To: Chris Dillon <cdillon@tri-lakes.net> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Weird ping behavior Message-ID: <Pine.BSF.3.96.970409184545.26130D-100000@ns2.harborcom.net> In-Reply-To: <334B2627.41C67EA6@tri-lakes.net>
next in thread | previous in thread | raw e-mail | index | archive | help
2.2 has a newer resolver library that discards invalid hostnames. This helps prevent security problems for programs that trust DNS data without doing any sanity checking. Bug the hostmaster of the losing domain to RTFRFC. pbd -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. On Wed, 9 Apr 1997, Chris Dillon wrote: > I am having a similar problem on my machine since upgrading (err, > updating <grin>) from 2.1.6 to 2.2. I thought it was just something I > did wrong in the update procedure and dismissed it as such, but if > others are having similar problems, maybe it needs to be looked into. > :-) > > My problem, however, extends much farther than just ping. Telnet and > ftp are affected as well. I fixed the same problem that occurred with > my installed ports leftover from my 2.1.6 install, such as ircii and > ncftp2, by compiling a "fakelib" of sorts found in the source tree > (forgot its exact name) which ALSO helped ftp/ping/telnet/etc. for some > reason? However, I didn't think any such problems should have affected > something like ping/ftp/telnet since they were compiled to run with any > new changes in 2.2 to begin with. :/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970409184545.26130D-100000>