On Tue, 21 Nov 2000, Joi Ellis wrote:

> On 22 Nov 2000, Juergen Kreileder wrote:
> 
> > It's not that easy.  A host may have several IP addresses and other
> > hosts may have to use different addresses to reach it.  E.g. hosts on
> > the intranet may have to use 192.168.0.100, but external machines may
> > have to use 65.123.66.124.
> 
> This is true, but it is not allowed in DNS for one host to have multiple
> addresses.  At least the DNS admin at my previous job claimed this was so.
> If you give each interface a DNS entry, each name must be unique.

With 4.9.3 it became possible to specify several A records for a given DNS
name. We were doing that for load balancing at my previous place. See the
following extract from DNS-HOWTO:

<extract>
3. How do I make DNS rotate through the available addresses for a
   service, say www.busy.site to obtain a load balancing effect, or
   similar?


   Make several A records for www.busy.site and use bind 4.9.3 or
   later.  Then bind will round-robin the answers.  It will not work
   with earlier versions of bind.
</extract>

> 
> Even if you have an internal DNS with one address, and an external DNS with
> a different address, when your own host looks itself it, it can only get
> one A record back.
>
> So, if what I understand of DNS is true, it is just that easy.
> 
> 

I think for all practical purposes the value returned by
getInetAddress() will be sufficient. A computer will be having n number
of interfaces and all of them need not be in the DNS record (or hosts 
file). But the program at the other end will be able to know through
which interface the connection is being made. So in the worst case one can
think about retrieving the IP of "this side" from that program ;-)

   Anil





----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to