Project

General

Profile

Actions

Bug #9564

closed

Dynamic DNS Status - IPv4 format error for 'Cached IP'

Added by Eric Veum over 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Dynamic DNS
Target version:
Start date:
05/29/2019
Due date:
% Done:

100%

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

Description

On the service dashboard, the 'Dynamic DNS status' is not printing the correct IPv4. The underlying service appears to still be working.

Current DDNS provider is namecheap, and the pfsense FW is reporting correctly still to the service, and I am able to do an internet query and see the extenral pfsense FW as reported for the DDNS records. All is goo there.

So I think the error is constrained to a UI problem for the Dashboard, or similar.
Instead of showing the IPv4 IPADDR, the DDNS status is showing "N/A" and the 'HH:MM:SS' date of when the cached IP is last checked. It used to show the IPv4 address instead.


Files

pfsense_dynamic_dns_status.png (45.3 KB) pfsense_dynamic_dns_status.png Eric Veum, 05/29/2019 10:51 AM
Actions #1

Updated by Eric Veum over 2 years ago

2.5.0-DEVELOPMENT - running the current dev branch

Actions #2

Updated by Jim Pingle over 2 years ago

  • Category set to Dynamic DNS
  • Status changed from New to Confirmed
  • Assignee set to Jim Pingle
  • Target version set to 2.5.0
  • Affected Version set to 2.5.0
  • Affected Architecture All added
  • Affected Architecture deleted ()

Confrimed here as well. It appears to only affect Namecheap, my others are working as expected. The status on services_dyndns.php is correct.

Actions #3

Updated by Jim Pingle over 2 years ago

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100
Actions #4

Updated by Jim Pingle about 2 years ago

  • Status changed from Feedback to Resolved

Still working fine with my Namecheap entries which failed before.

Actions

Also available in: Atom PDF