Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!TWG.COM!dcrocker
From: dcrocker@TWG.COM (Dave Crocker)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Multiple TCP/IP servers on one host
Message-ID: <8809080134.AA05073@ucbvax.Berkeley.EDU>
Date: 7 Sep 88 15:22:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 14

There seems to be some convergence on the use of the domain name service
ip address list, as a means of accessing multiple interfaces (with one 
interface per milking machine) to the same service host.  A couple of
notes, however, have mentioned reliance on a feature that is not
supported:  having the domain name service select which ip address to 
give you, thereby having the DNS do the randomization necessary to give
load-leveling.

Selection of the "correct" IP address must be done by the client (e.g.,
telnet).  The DNS has no way of knowing what use you will put the information
to and it has no way of distinguishing multiple milking machines from
multiple connections to different parts (i.e., different networks) on
an internet.

Dave