[27802] in North American Network Operators' Group
Re: Alternative to BGP-4 for multihoming?
daemon@ATHENA.MIT.EDU (Randy Bush)
Tue Mar 14 11:19:15 2000
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Joe Loiacono <jloiacon@nastg.gsfc.nasa.gov>
Cc: nanog@merit.edu
Message-Id: <E12UtzR-0003sA-00@rip.psg.com>
Date: Tue, 14 Mar 2000 08:16:13 -0800
Errors-To: owner-nanog-outgoing@merit.edu
> Once the client's DNS request has worked its way over to the primary DNS
> for the distributed web-servers, 3DNS has each of the other 3DNS boxes
> (located adjacent to the other distributed servers) ping the *clients*
> primary DNS. 3DNS then returns the URL for the web-server whose 3DNS
> machine is 'closest' (fewest hops) to the clients DNS machine.
you may want to seriously reread the previous sender's message. the point
is that in the modern post-2182 world, many of the client's nameservers are
vastly net.distant from the client.
psg.com nameserver = DNS.LIBRARY.UCLA.EDU
psg.com nameserver = RAIN.PSG.COM
psg.com nameserver = ARIZONA.EDU
it is best common practice.
randy
