[lvs-users] Bind not listening on new ip after failover

Malte Geierhos malte at snapscouts.de
Sun May 17 14:35:07 BST 2009


Hi,

it should work with

net.ipv4.ip_nonlocal_bind = 1

in your sysctl.conf (please apply with sysctl -p afterwards)
then your bind9 can bind to any non local ip i.e.  the vip of your 2nd 
server.
Complications do not occur. (In terms of the local server answering 
instead of the remote) as long
as the corresponding interface isn't up & running.

regards,
Malte Geierhos

Stefan Pöter schrieb:
> Hi,
>
> i have heartbeat and ldirectord running on two nodes with an ldap server 
> and a bind9 server. Everthing works fine until i switch one of these 
> servers down (they are also my routers for the internet). When that 
> happens bind9 won't resolve any dns request. After I restart bind9 
> manualy on the active node its working fine again. The Problem is, that 
> it won't listen to the new network adresse that it got from heartbeat.
>
> Is there any possibility that i can tell heartbeat or the ldirectord to 
> restart bind9 on a failover? Or is there any other option i can choose?
>
> Thanks and greetings,
> Steve
>
> _______________________________________________
> Please read the documentation before posting - it's available at:
> http://www.linuxvirtualserver.org/
>
> LinuxVirtualServer.org mailing list - lvs-users at LinuxVirtualServer.org
> Send requests to lvs-users-request at LinuxVirtualServer.org
> or go to http://lists.graemef.net/mailman/listinfo/lvs-users
>   






More information about the lvs-users mailing list