From owner-freebsd-stable Thu Apr 22 14: 4:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp3.erols.com (smtp3.erols.com [207.172.3.236]) by hub.freebsd.org (Postfix) with ESMTP id 82EB11518A for ; Thu, 22 Apr 1999 14:04:05 -0700 (PDT) (envelope-from jcanon@comtechnologies.com) Received: from comtechnologies.com (207-172-71-191.s64.as7.frd.va.dialup.rcn.com [207.172.71.191]) by smtp3.erols.com (8.8.8/8.8.5) with ESMTP id RAA24951; Thu, 22 Apr 1999 17:01:05 -0400 (EDT) Message-ID: <371F8E10.F57F11A@comtechnologies.com> Date: Thu, 22 Apr 1999 17:01:04 -0400 From: Jason Canon X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: David Schwartz Cc: Igor Roshchin , stable@freebsd.org Subject: Re: netstat -r References: <000301be8cfc$35aab620$021d85d1@whenever.youwant.to> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I have to concede that it is impossible to argue scientifically against with a position that says "It was working by pure luck...". Either you forgot that the Internet ran for about a decade before DNS came along or perhaps the word "newby" (as in you were not around then) may be applicable. Otherwise, perhaps you can quote the applicable RFC and/or BSD documentation that supports your assertion that it is a requirement that networks operate a private DNS server. Agreeably, the configuration requirements, for those who choose to run DNS, for both public gateway and private network domains is widely known so all you need to cite is the standard that says /etc/hosts is insufficient because (x). Thanks, Jason David Schwartz wrote: > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message