> So it wouldn't be perfect, but it would probably work decently as a > fail-over.
Considering that there's no other way other than short TTLs to do geographic load-balancing w/failover -- even mega-hitting GLB hardware has a rather explicit reliance on the TTLs it gives out based on response time probes and so on -- I'd say it's as perfect as the DNS part of load-balancing can ever be. > Note that this setup won't do hardly anything as far as load > balancing goes since primary should always be hit first unless there > is an issue (connectivity or RFC compliance). Er, no... that isn't the way NS records are used. Recursors looking up your NS records do not "know" that you went to Dotster or whatever and entered ns1 before ns2. The NS records handed out by the roots are used by recursors in what can be called a random order (the order actually has to do with response time as well, but assuming for the moment unsaturated bandwidth and identical hardware at both sites, you can call it random). --Sandy ------------------------------------ Sanford Whiteman, Chief Technologist Broadleaf Systems, a division of Cypress Integrated Systems, Inc. e-mail: [EMAIL PROTECTED] SpamAssassin plugs into Declude! http://www.imprimia.com/products/software/freeutils/SPAMC32/download/release/ Defuse Dictionary Attacks: Turn Exchange or IMail mailboxes into IMail Aliases! http://www.imprimia.com/products/software/freeutils/exchange2aliases/download/release/ http://www.imprimia.com/products/software/freeutils/ldap2aliases/download/release/ --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
