GSLB with RHI can work if your design permits it. Scott
On Tue, Jun 15, 2010 at 11:42 AM, Lazuardi Nasution <[email protected]>wrote: > Hi Scott, > > I think reordering the DNS record on GSLB only help for distributing > the first clients access. But, if one VIP which is previously accessed > by clients is failed, GSLB cannot help since the IE still cache the > failed VIP address and do not do DNS query until 30 minutes. In other > words, GSLB is useless if the browser still use their own DNS cache. > Any other opinion ? > > Best regads, > > > From: "Scott T. Cameron" <[email protected]> > > To: [email protected] > > Date: Tue, 15 Jun 2010 10:28:25 -0400 > > Subject: Re: [f-nsp] GSLB vs IE DNS Cache > > DNS caching is a problem you'll face in more than just IE, but most > applications that ever look up a DNS record will cache the record for some > period of time -- if not indefinitely. > > There is no easy solution to that problem, except informing your > customers to shut down the application and restart it. > > Your design for your customer facing applications will really determine > the best way to use GSLB, and you may not ever need to run in to DNS caching > problems -- design permitting. > > Scott > > On Tue, Jun 15, 2010 at 10:05 AM, Lazuardi Nasution < > [email protected]> wrote: > >> > >> Hi, > >> > >> In my understanding, the GSLB works by doing some ordering of DNS > >> records. The problem is the IE browser is doing DNS cache about 30 > >> minutes regardless to the TTL and always use first DNS record without > >> trying to use next DNS records. How can we encounter this problem > >> without touching the client PCs ? > >> > >> Best regards, > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp >
_______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
