May 5 17:39:32 php-fpm 86989 /services_dyndns_edit.php: Dynamic DNS noip (dh.): 24.134.97.169 extracted from Check IP Service May 5 17:39:32 php-fpm 86989 /services_dyndns_edit.php: Dynamic DNS: updatedns() starting
#No ip duc service not starting update#
May 5 17:35:48 php-fpm 2717 /services_dyndns_edit.php: phpDynDNS (dh.): (Success) IP address is current, no update performed. Notice following logs: May 5 17:35:48 php-fpm 2717 /services_dyndns_edit.php: phpDynDNS: updating cache file /conf/dyndns_lannoip'dh.'1.cache: 24.134.97.169 Looks like its a parsing issue as the username is 'GROUPNAME:USERNAME' (thats a way to have multiple tenants on a single no-ip account).Ĭreate new dyndns hostname in no-ip web-interface. As Viktor pointed out, it may be something with the API change we made in 2.5.0, but the logs would seem to indicate that the WAN IP just didn't change as far as pfSense can tell. Whatever is going on here isn't systemic in the DynDNS client. Tested with Afraid Free DNS and a RFC2136 DynDNS client and these both work just fine. Php-fpm 59326 /services_dyndns_edit.php: phpDynDNS (): (Success) IP address is current, no update performed. Php-fpm 59326 /services_dyndns_edit.php: phpDynDNS: updating cache file /conf/dyndns_wannoip''0.cache: XX.XX.XX.XX Php-fpm 59326 /services_dyndns_edit.php: Dynamic DNS noip (): XX.XX.XX.XX extracted from local system. Php-fpm 59326 /services_dyndns_edit.php: Dynamic DNS noip (): _checkStatus() starting. With new IP is YY.YY.YY.YY, and old IP XX.XX.XX.XX it is in log:
No Target - New Issues (Base and Packages).No Target - All Open Issues (Base Only).New Issues by Category - No Target+Future.CE-Next - Feedback (Likely needs target changed).CE-Next - All Closed Issues (Move to specific target).22.05 Plus - New/Confirmed/In Progress Issues.21.05.1 Plus Target - All Closed Issues.
0 kommentar(er)
