Newsgroups: comp.unix.internals
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!theory.tn.cornell.edu!shore
From: shore@theory.tn.cornell.edu (Melinda Shore)
Subject: Re: Shared libraries
Message-ID: <1991May7.145228.423@batcomputer.tn.cornell.edu>
Sender: news@batcomputer.tn.cornell.edu
Nntp-Posting-Host: theory.tn.cornell.edu
Organization: Cornell Theory Center
References: <kre.673335935@mundamutti.cs.mu.OZ.AU> <1991May4.132632.13885@mp.cs.niu.edu> <161@titccy.cc.titech.ac.jp>
Date: Tue, 7 May 1991 14:52:28 GMT

In article <161@titccy.cc.titech.ac.jp> mohta@necom830.cc.titech.ac.jp (Masataka Ohta) writes:
>The reality is a bit different. With DNS, it is common that a signle hostname
>have multiple IP addresses.

The two things are entirely independent.  It is not true that there
is any relationship between name service and the number of IP addresses
on a single host, and it is absolutely not true that it is common for
a host to have multiple IP addresses.  Unless, of course, your definition
of "common" is radically different.

>Programs were modified so that they try all
>possible addresses, because it was common that some of IP addresses are
>often unreachable because of a routing problem.

Again, this is independent of the mechanism used for hostname lookup.
In the musty, dusty days before name service I had to fix the routing
code in a hyperchannel driver for just this reason.
-- 
                    Software longa, hardware brevis
Melinda Shore - Cornell Information Technologies - shore@theory.tn.cornell.edu
