Project

General

Profile

Actions

Bug #6992

closed

ZoneEdit DDNS does not update to CARP IP

Added by James Kohout over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Category:
Dynamic DNS
Target version:
Start date:
12/07/2016
Due date:
% Done:

100%

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

Description

When using ZoneEdit Dynamic DNS, using dual wan with a gateway group for failover, ZoneEdit domain gets the WAN/Interface IP instead of the CARP IP.
Logs show that it should be updating with the CARP IP, but when you login to zoneedit it has the WAN/Interface IP.
For example:
/rc.dyndns.update: Dynamic DNS: updatedns() starting
Dec 7 11:21:34 php-fpm 11826 /rc.dyndns.update: Dynamic DNS zoneedit (remote.active-semi.us): 216.74.227.26 extracted from local system.
Dec 7 11:21:34 php-fpm 11826 /rc.dyndns.update: Dynamic DNS (remote.active-semi.us): running get_failover_interface for remoteFailover. found _vip583af5f91f885
Dec 7 11:21:34 php-fpm 11826 /rc.dyndns.update: Dynamic DNS zoneedit (remote.active-semi.us): 216.74.227.26 extracted from local system.
Dec 7 11:21:34 php-fpm 11826 /rc.dyndns.update: Dynamic Dns (remote.active-semi.us): Current WAN IP: 216.74.227.26 Cached IP: 216.74.227.26
Cached IP shows .26 on the status screen, but login to zone edit shows 216.74.227.29, which is the WAN/Interface IP for the one router.
It does update the IP when switching over between WAN interfaces and doing updates, so it is communicating with Zone Edit - but it is giving the wrong IP address.

I tried the exact same setup using DynDNS as at test case, and DynDNS works correctly, and get the correct Cached IP. So it looks like it is something with the ZoneEdit configuration/setup.

Actions

Also available in: Atom PDF