[91126] in North American Network Operators' Group
RE: DNS Based Load Balancers
daemon@ATHENA.MIT.EDU (Joseph Jackson)
Wed Jul 5 03:00:21 2006
Date: Tue, 4 Jul 2006 23:59:17 -0700
From: "Joseph Jackson" <JJackson@aninetworks.com>
To: "Lincoln Dale" <ltd@interlink.com.au>,
"Rodrick Brown" <rodrick.brown@gmail.com>,
"Sam Stickland" <sam_mailinglists@spacething.org>
Cc: "Matt Ghali" <matt@snark.net>,
"Patrick W. Gilmore" <patrick@ianai.net>, <nanog@merit.edu>
Errors-To: owner-nanog@merit.edu
This is a multi-part message in MIME format.
------_=_NextPart_001_01C6A000.8860C02C
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
What would be a better solution then?
-----Original Message-----
From: Lincoln Dale [mailto:ltd@interlink.com.au]
Sent: Tue Jul 04 18:30:00 2006
To: 'Rodrick Brown'; 'Sam Stickland'
Cc: 'Matt Ghali'; 'Patrick W. Gilmore'; nanog@merit.edu
Subject: RE: DNS Based Load Balancers
> As someone who has also deployed GSLB's with hardware applicances I
> would also like to know real world problems and issues people are
> running into "today" on modern GSLB implementations and not
> theoretical ones, as far as I can tell our GSLB deployment was very
> straight forward and works flawlessly.
GSLB based on DNS have one significant shortcoming that moone here has =
yet
mentioned: they are performing their magic on the location of the
_nameserver_ that issued the query.
this can be VERY different to that of the ACTUAL location of the client.
for example, Akamai always sends to off to a serverfarm in Northern
California, because that's where my DNS query is originating from.
that is almost the exact opposite side of the planet from where I'm =
coming
from.......
irony is that there is an akamai cluster about 10 feet away from where =
my
[subsequent] http requests originate from...
sure - perhaps this isn't the norm - split-tunnel VPNs being what they =
are -
but it's a perfect example of why GSLB based on DNS ain't perfect.
cheers,
lincoln.
------_=_NextPart_001_01C6A000.8860C02C
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>RE: DNS Based Load Balancers</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=3D2>What would be a better solution then?<BR>
<BR>
-----Original Message-----<BR>
From: Lincoln Dale [<A =
HREF=3D"mailto:ltd@interlink.com.au">mailto:ltd@interlink.com.au</A>]<BR>=
Sent: Tue Jul 04 18:30:00 2006<BR>
To: 'Rodrick Brown'; 'Sam Stickland'<BR>
Cc: 'Matt Ghali'; 'Patrick W. Gilmore'; =
nanog@merit.edu<BR>
Subject: RE: DNS Based Load =
Balancers<BR>
<BR>
<BR>
> As someone who has also deployed GSLB's with hardware applicances =
I<BR>
> would also like to know real world problems and issues people =
are<BR>
> running into "today" on modern GSLB implementations and =
not<BR>
> theoretical ones, as far as I can tell our GSLB deployment was =
very<BR>
> straight forward and works flawlessly.<BR>
<BR>
GSLB based on DNS have one significant shortcoming that moone here has =
yet<BR>
mentioned: they are performing their magic on the location of the<BR>
_nameserver_ that issued the query.<BR>
<BR>
this can be VERY different to that of the ACTUAL location of the =
client.<BR>
<BR>
for example, Akamai always sends to off to a serverfarm in Northern<BR>
California, because that's where my DNS query is originating from.<BR>
<BR>
that is almost the exact opposite side of the planet from where I'm =
coming<BR>
from.......<BR>
irony is that there is an akamai cluster about 10 feet away from where =
my<BR>
[subsequent] http requests originate from...<BR>
<BR>
sure - perhaps this isn't the norm - split-tunnel VPNs being what they =
are -<BR>
but it's a perfect example of why GSLB based on DNS ain't perfect.<BR>
<BR>
<BR>
<BR>
cheers,<BR>
<BR>
lincoln.<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C6A000.8860C02C--
