Thanks for the quick reply. rndc reconfig has the same problem as a restart. I need to automatically listen to the new ip address without manual intervention. On Wed, 2013-06-05 at 09:14 +0100, Phil Mayers wrote: > On 06/05/2013 07:37 PM, paul wrote: > > Hi. I have a two node active passive cluster serving webpages. When a > > failover occurs, I have to restart named on the now active node because > > You don't have to restart it. "rndc reconfig" will re-check the IPs on > the machine and re-listen. > > > the cluster Ip was not available when named originally started even > > though I have listen-to the cluster ip listed in my named.conf. Is there > > a way to make named listen-to an ip address that is not yet available? > > No. This has come up before - the bind listen-on statement is an ACL > which is matched against the list of IPs on the box, not a list of IPs > passed to the bind() syscall. There are various solutions, but "rndc > reconfig" is the right one IMO. > _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe > from this list > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
