next gen h2n

[kevinm at crt.com]

Just out of curiousity (SP?), if this is a *nix environment (which it
appears it must be) would there be a good reason not to setup NIS so you
wouldn't HAVE to maintain the /etc/hosts file on every one of 100 computers?
Then setup the necessary switch file to point hosts info only to "nis dns
files" or "dns nis files"?

Kevin Martin
kevinm at crt.com

-----Original Message-----
From: Jim Reid [mailto:jim at rfc1035.com]
Sent: Sunday, March 12, 2000 3:11 PM
To: Lars Hecking
Cc: Kevin Darcy; comp-protocols-dns-bind at moderators.isc.org
Subject: Re: next gen h2n 


>>>>> "Lars" == Lars Hecking <lhecking at nmrc.ucc.ie> writes:

    Lars>  There's nothing intrinsically "broken" with hosts files.

This must qualify as one of the silliest statements that I have ever
seen. Have you ever tried to keep this file consistent across a
non-trivial (say 100) number of systems? What if some of them are not
under your administrative control? Try keeping the same /etc/hosts
file on every box on a university campus for instance..... And the EE
department doesn't want to get the CS department logs in their local
syslog server, loghost. And vice-versa. Likewise for WWW, mail, NFS,
news, etc, etc. Or if some software install utility adds names to the
file for the thing it's just installed on someone's personal
workstation.