Project

General

Profile

Actions

Bug #10850

closed

GoDaddy (v6) returns error when creating or updating

Added by Michael Virgilio about 1 year ago. Updated about 1 year ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Dynamic DNS
Target version:
-
Start date:
08/23/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.5-p1
Affected Architecture:

Description

When creating or updating a DDNS entry using "GoDaddy (v6)" as the service, the following entries appear in the system logs when verbose logging is enabled:

Aug 23 11:49:00 php-fpm 18000 /services_dyndns_edit.php: Dynamic DNS: updatedns() starting
Aug 23 11:49:00 php-fpm 18000 /services_dyndns_edit.php: Dynamic DNS godaddy-v6 (host.domain.com): 2001:xxxx:yy:zzz::a extracted from local system.
Aug 23 11:49:00 php-fpm 18000 /services_dyndns_edit.php: Dynamic DNS (host.domain.com): running get_failover_interface for opt2. found gif0
Aug 23 11:49:00 php-fpm 18000 /services_dyndns_edit.php: Dynamic DNS godaddy-v6 (host.domain.com): _update() starting.
Aug 23 11:49:00 php-fpm 18000 /services_dyndns_edit.php: Dynamic DNS godaddy-v6 (host.domain.com): _checkStatus() starting.
Aug 23 11:49:00 php-fpm 18000 /services_dyndns_edit.php: phpDynDNS (host): PAYLOAD:
Aug 23 11:49:00 php-fpm 18000 /services_dyndns_edit.php: phpDynDNS (host): (Unknown Response)

The entry is not created or updated on GoDaddy's end, and the cache data for the entry in pfSense shows ::

The regular "GoDaddy" service for IPv4 works fine.

And yes, I realize that the address of my GIF0 interface isn't going to change... it's the only external IPv6 interface I have at the moment, and when my ISP starts supporting IPv6 via DHCP-PD, I want to make sure DDNS will be working too. I use the hostname to do ping availability/latency checks from an outside host.

Actions #1

Updated by Michael Virgilio about 1 year ago

Yet I can do the exact same thing with LAN (ix1) as the interface, which is also static (since I'm using a HE tunnel right now), and it works fine. So maybe something about how it reads the address from certain interface types? Though the address it shows on the second line in that log clip is in fact the correct address. Maybe it reads that for OPT2 and not GIF0? I don't know... just reporting the bug. :)

Actions #2

Updated by Viktor Gurov about 1 year ago

  • Affected Version set to 2.4.5-p1

seems the same issue as #8432

dyndns client tries to use parent interface instead of gif/lagg etc.

Actions #3

Updated by Michael Virgilio about 1 year ago

Ok, looks like this can be closed then, since it's a duplicate. Sorry for that, didn't realize!

Actions #4

Updated by Jim Pingle about 1 year ago

  • Status changed from New to Duplicate
Actions

Also available in: Atom PDF