Secondary in failover pair does not perform dynamic DNS updates
rharolde at umich.edu
Tue Apr 4 19:16:35 UTC 2017
On Tue, Apr 4, 2017 at 2:29 PM, Matthew Kassawara <
matthew.kassawara at blinker.com> wrote:
> Neither stopping the primary peer (resulting in a
> "communications_interrupted" state on the secondary peer) nor changing the
> primary peer state to "partner_down" via OMAPI cause the secondary peer to
> perform dynamic DNS updates.
> On Tue, Apr 4, 2017 at 12:22 PM, Simon Hobson <dhcp1 at thehobsons.co.uk>
>> Matthew Kassawara <matthew.kassawara at blinker.com> wrote:
>> > If I simulate failure of the primary DHCPD instance
>> Are you doing that properly, and putting the peer into partner down state
You need to do "partner_down" on the secondary (telling it the primary is
down). It might get to that state after waiting the MCLT time (typically a
half hour ?) but I am not sure. So "complete" failover is a manual process.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dhcp-users