Project

General

Profile

Actions
Copy link

Bug #9435

closed

Dynamic DNS Update events do not occur after certain failover event cases

Added by Chris Linstruth about 5 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
Dynamic DNS
Target version:
2.5.0
Start date:
03/26/2019
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.5.0
Affected Architecture:

Description

This test was done on a lab HA pair behind a NAT router (so check_ip service is needed.)

Failover group FAILOVER
WAN_GW Tier 1 WAN CARP VIP
WAN2_GW Tier 2 WAN2 CARP VIP

Dynamic DNS on HE.NET bound to the FAILOVER group. Works.

Block pings upstream for WAN
Failover event triggers
DynDNS entry shows WAN public address in red

DynDNS update is not triggered

Running this php code updates everything to WAN2 and green

$failover_group_name = 'FAILOVER';

services_dyndns_configure($failover_group_name);
services_dnsupdate_process($failover_group_name);

Dynamic DNS: updatedns() starting
is not logged until the php is run.

The same thing happens on fail back.

Not sure. It could be that all static addresses + multi-wan + dyndns ( + HA?) are rare enough this isn't hit more often.

Actions
Copy link

Also available in: Atom PDF