One Domain; Multiple IPs.

[Brad Knowles]

At 12:25 AM +0000 7/19/01, Barry Margolin wrote:

>  With an anycasting system, the IP address could suddenly be redirected to a
>  totally different server farm, because the routing table now makes that
>  farm seem closer.

	Okay, fine.  Use anycasting to get to the closest F5 BigIP (or 
similar device) that uses TCP triangulation to cause the connection 
to continue to be set up to a the local load-balancing device 
(presumably set up in dual HA fail-over mode with a backup, which 
would even steal the MAC address of its mate if it ever died), after 
which routing table changes would not have the effect of directing 
you to a different site.

	Then have the load-balancing switch distribute the incoming 
connections across the set of back-end servers, handling failover, 
smooth close-down and ramp-up of back-end servers, etc....


	You should even be able to combine the two 
load-balancing/distribution devices into one, if you like.


	This still avoids the abuse and mis-use of the DNS to solve 
problems it is ill-designed to handle.

-- 
Brad Knowles, <brad.knowles at skynet.be>

/*        efdtt.c  Author:  Charles M. Hannum <root at ihack.net>          */
/*       Represented as 1045 digit prime number by Phil Carmody         */
/*     Prime as DNS cname chain by Roy Arends and Walter Belgers        */
/*                                                                      */
/*     Usage is:  cat title-key scrambled.vob | efdtt >clear.vob        */
/*   where title-key = "153 2 8 105 225" or other similar 5-byte key    */

dig decss.friet.org|perl -ne'if(/^x/){s/[x.]//g;print pack(H124,$_)}'