Bug #9435
closed
Dynamic DNS Update events do not occur after certain failover event cases
100%
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.
Updated by Viktor Gurov almost 4 years ago
Updated by Jim Pingle almost 4 years ago
- Status changed from New to Pull Request Review
- Target version set to 2.5.0
Updated by Renato Botelho almost 4 years ago
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
PR has been merged. Thanks!
Updated by Ronald Schellberg almost 4 years ago
The PR/Commit is triggering PHP errors on booting, see "PHP Errors after latest update (amd64) built on Thu Jun 11 13:02:15 EDT 2020"
Updated by Viktor Gurov almost 4 years ago
Ronald Schellberg wrote:
The PR/Commit is triggering PHP errors on booting, see "PHP Errors after latest update (amd64) built on Thu Jun 11 13:02:15 EDT 2020"
Updated by Ronald Schellberg almost 4 years ago
Thanks. Manually applied the commit and PHP dump is gone on reboot.
Updated by Jim Pingle almost 4 years ago
- Status changed from Feedback to Pull Request Review
Updated by Jim Pingle almost 4 years ago
- Status changed from Pull Request Review to Feedback
PR merged
Updated by Anonymous