Hi All
Thanks for all your answers, I agree it would be better with heartbeat then
to mock around with dns and a very slow update time.
Regards
Per Qvindesland
On 2/20/09 2:08 PM, "Tim Verhoeven" <tim.verhoeven.be@xxxxxxxxx> wrote:
> On Fri, Feb 20, 2009 at 1:29 PM, Per Qvindesland <per@xxxxxxxxxx> wrote:
>>
>> I've two servers running the same ldap service. A is primary server and B is
>> simply a mirror, and accounts from server A are constantly synchronized with
>> B.
>>
>> Now I don't have a automatic failover solution, whenever server A goes down,
>> I have to point the domain's A record to server B and wait for the DNS to
>> get updated. Takes quite a lot of time but the ldap service is crucial to
>> the system and shouldn't be down for longer than a few minutes.
>>
>> I've heard about Dyndns? They provide automatic failover if one server does
>> down, what I want to know is if I can do the same using Bind? And if it's
>> possible to do it automatically? Without human intervention.
>>
>> I don't want a round-robin solution, I want a automatic switchover if
>> primary box goes down.
>
> I also recommend you use a service IP address that can be migrated
> between your 2 servers. You can use heartbeat to automate that or do
> that manually as you are doing now. But moving a service IP is much
> simpler and faster. Stay away from using DNS to manage the failover.
> As you said is can take a while.
>
> Regards,
> Tim
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
