route traffic to global datacenters using DNS

cindyjohnson1 at verizon.net cindyjohnson1 at verizon.net
Wed Feb 27 12:11:16 UTC 2008


Or you could buy a GSS from Cisco.
http://www.cisco.com/en/US/products/hw/contnetw/ps4162/index.html

We have all three in our Network (F5, Foundry and Cisco); just mentioning the options.
Good Luck!
Cindy

From: Fr34k <freaknetboy at yahoo.com>
Date: 2008/02/26 Tue AM 07:30:40 CST
To: comp-protocols-dns-bind at isc.org
Subject: Re: route traffic to global datacenters using DNS

Depending upon your needs, you may find a cheaper alternative with Foundry:

http://www.foundrynet.com/solutions/sol-app-switch/
http://www.foundrynet.com/solutions/sol-app-switch/sol-dns/



----- Original Message ----
From: Dawn Connelly <dawn.connelly at gmail.com>
To: stevehunter_1 at hotmail.com
Cc: comp-protocols-dns-bind at isc.org
Sent: Tuesday, February 26, 2008 3:02:16 AM
Subject: Re: route traffic to global datacenters using DNS

If you want all of this to happen dynamically it sounds like you are looking
for Global Traffic Managers by F5.
http://www.f5.com/products/big-ip/product-modules/global-traffic-manager.html
They aren't free but they will do exactly what you are looking for. You can
set them up to poll the individual servers for various criteria- how many
sessions, server resources, availability, etc. The way we did it in our
environment was set up a subdomain that the GTM servers were authoritative
for and them created CNAME records that pointed to that subdomain. So say
resource.example.com was an application that sits behind a GTM. We'd create
a CNAME record that pointed resource.example.com to
resource.gtm.example.comand have
gtm.example.com delegated to the GTM servers. It has worked incredible well
for us.

On Sat, Feb 23, 2008 at 10:29 PM, <stevehunter_1 at hotmail.com> wrote:

> Scenario:
> 2 Datacenters at two different geographic regions.
> Each datacenter has its own set of DNS servers (lets say 2)
>
> If I assign nameservers to a domain name in the following order:
> location1A
> location1B
> location2A
> location2B
>
> For "failover", it would be logical that the DNS for location1A would
> point to servers at location#1.  So if location#1 failed, DNS servers
> 1A and 1B would be down, and DNS servers for 2A and 2B would pick up
> the traffic and they would route to servers at location#2.
>
> This is all fine and with a TTL of one minute would work very well.
> But what if I wanted to load balance (round robin) to location1 and
> location2?
>
> So location1A DNS server would round robin to location1 and
> location2.  What happens when location2 goes down, how do you fix
> this?  Because location1A DNS is still going to hand our location#2 IP
> addresses ...  what are the real-world examples?  manually changing
> the DNS is a solution, but not a fast solution.  What tools or
> techniques are people using?  I am sure this has been addressed before
> but I could not find any information on it.
>
> So the requirement I have is to load balance (round robin), TTL of a
> minute or less, and to incorporate some type of failover using the
> DNS.
>
> Thanks for any assistance
>
>



More information about the bind-users mailing list