Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Apr 1999 17:01:04 -0400
From:      Jason Canon <>
To:        David Schwartz <>
Cc:        Igor Roshchin <>,
Subject:   Re: netstat -r
Message-ID:  <>
References:  <000301be8cfc$35aab620$>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

I have to concede that it is impossible to argue scientifically against with a
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).


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
> with "unsubscribe freebsd-stable" in the body of the message

To Unsubscribe: send mail to
with "unsubscribe freebsd-stable" in the body of the message

Want to link to this message? Use this URL: <>