Date: Thu, 22 Apr 1999 13:10:47 -0700 From: "David Schwartz" <davids@webmaster.com> To: "Jason Canon" <jcanon@comtechnologies.com> Cc: "Igor Roshchin" <igor@physics.uiuc.edu>, <stable@freebsd.org> Subject: RE: netstat -r Message-ID: <000301be8cfc$35aab620$021d85d1@whenever.youwant.to> In-Reply-To: <371F806E.57FABC85@comtechnologies.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It was working by pure luck -- the IPs happened to not resolve. There are no such guarantees. The configuration was always broken. It was always trying to do something it shouldn't do -- namely resolve private IPs on the global Internet. The fix is to make all nameservers used by machines in private IP space able to resolve those private IPs correctly. DS > Ordinarily I would agree with you completely but what Igor and I are both > saying is that something external to our environments (e.g., IANA) appears > to have been the source. My /etc/hosts file contains resolution > for all private > IPs in use on the LAN. This has been working fine for almost 1 year but > during the past 24 hours or so the server ignored the hosts file > and printed > an IANA resolution instead. 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?000301be8cfc$35aab620$021d85d1>