There is not (yet) a GSLB or dyndns daemon available in opensource,
but a few DNS server could be used to emulate this feature.
- PowerDNS  + pipe backend
- unbound + python module

or yourself updating your DNS server to trigger a failover


Cheers


On Tue, Nov 1, 2011 at 6:10 PM, Senthil Naidu <senthil.na...@gmail.com> wrote:
> hi,
>
> we need to have a setup as follows
>
>
>
> site 1                                                     site 2
>
>       LB  (ip 1)                                   LB (ip 2)
>        |                                                   |
>        |                                                   |
>  srv1  srv2                                      srv1 srv2
>
> site 1 is primary and site 2 is backup in case of site 1  LB's failure or
> failure of all the servers in site1 the website should work from backup
> location servers.
>
> Regards
>
> On Tue, Nov 1, 2011 at 10:31 PM, Gene J <gh5...@gmail.com> wrote:
>>
>> Please provide more detail about what you are hosting and what you want to
>> achieve with multiple sites.
>>
>> -Eugene
>>
>> On Nov 1, 2011, at 9:58, Senthil Naidu <senthil.na...@gmail.com> wrote:
>>
>> Hi,
>>
>> thanks for the reply,  if the same needs to be done with dns do we need
>> any external dns services our we can use our own ns1 and ns2 for the same.
>>
>> Regards
>>
>>
>> On Tue, Nov 1, 2011 at 9:06 PM, Baptiste <bed...@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> Do you want to failover the Frontend or the Backend?
>>> If this is the frontend, you can do it through DNS or RHI (but you
>>> need your own AS).
>>> If this is the backend, you have nothing to do: adding your servers in
>>> the conf in a separated backend, using some ACL to take failover
>>> decision and you're done.
>>>
>>> cheers
>>>
>>>
>>> On Tue, Nov 1, 2011 at 2:25 PM, Senthil Naidu <senthil.na...@gmail.com>
>>> wrote:
>>> > Hi,
>>> >
>>> > Is it possible to use haproxy in a active/passive failover scenario
>>> > between
>>> > multiple datacenters.
>>> >
>>> > Regards
>>> >
>>> >
>>> >
>>> >
>>
>
>

Reply via email to