Max Williams wrote:
Hi,
I have a pair of clustered DNS servers with a virtual IP (VIP) configured. The
problem is that when the VIP fails over, named on the new host of the VIP will
not listen on port 53/UDP of the VIP until it is reloaded (I think this is
because this daemon uses UDP, not TCP).
So I'd like to be able to reload named after a failover of the VIP address. Is
this possible?
I could do it by configuring named as a cloned resource and then configuring an
order so that it is restarted when the VIP fails over or moves but I would much
rather have named reload instead of restart.
Any ideas? I'd rather not have to resort to a wrapper script or anything like
that.
This seems to be a design decision on the part of the bind authors.
There is a parameter
options { interface-interval 1; };
that can be set (in minutes, lowest is 1 minute because 0 disables it)
to have bind rescan for new interfaces on the machine.
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
