Re: redundancy via DNS
Won't work unless your TTL is set extremely low, and even then other DNS
admins can override that on their servers and cache the "down" site.
Remember, not everyone comes back to you for an authoritative answer for
Using DNS for load-balancing is NOT a good idea, ever. Or RARELY is is
useful, and it's NOT good for distaster-recovery/redundancy switching.
On Tue, Jun 19, 2001 at 10:29:33AM -0400, Fraser Campbell wrote:
> ":yegon" <firstname.lastname@example.org> writes:
> > we have several servers colocated with several ISP's
> > i am trying to sort out some configuration that would ensure good uptime for
> > customers
> We're helping a customer with a similar situation. They have multiple
> incoming Internet connections. What we plan to do:
> - Have a DNS server for each Internet connection
> - Servers are replicated/available via every connection
> - Each DNS server gives out IPs only within it's subnet
> This way if one of the connections go down, that DNS server becomes available
> and those IPs stop being handed out ... effectively removing those IPs from
> your DNS rotation and automatically failing over to the remaining
> connections. This also provides a load balancing effect.
> To UNSUBSCRIBE, email to email@example.com
> with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
Nate Duehr <email@example.com>
GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.