Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!accuvax.nwu.edu!nucsrl!gore
From: gore@eecs.nwu.edu (Jacob Gore)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Reconciling /etc/hosts, yp, and named?
Message-ID: <7080017@eecs.nwu.edu>
Date: 19 May 89 03:59:24 GMT
References: <8905161521.AA02497@dsys.icst.nbs.gov>
Organization: Northwestern U, Evanston IL, USA
Lines: 26

>Root Boy Jim <rbj@DSYS.ICST.NBS.GOV> writes:
>
>	Simpler to just use one name, and use naked IP addresses on the
>	ifconfigs.

/ comp.protocols.tcp-ip / jordan@cs.columbia.edu (Jordan Hayes) / May 18 1989 /
>The DNS was created to make things easier.  Using IP addresses doesn't
>make things easier.  If you have two IP addresses on the same machine,
>name them uniquely and put the following data into your database:
>
>foo		IN	A	128.253.5.1
>		IN	A	128.253.6.1
>foo-gw		IN	A	128.253.6.1

For ifconfig's???

In order for this to work, the name server has to be running on THIS
machine, and you have to be able to launch it before you do the ifconfigs.
It seems that it's much easier to start up network programs after the
network interfaces are configured.

IP numbers may not "make things easier", but they are predictable.  I think
they are reasonable names for specific interfaces.

Jacob Gore				Gore@EECS.NWU.Edu
Northwestern Univ., EECS Dept.		{oddjob,chinet,att}!nucsrl!gore