I guess I've added them myself somewhere in the past. Tell us what you did wrong, and we'll tell you what you did wrong )Įdit : these log lines seem messy to me. services_dyndns_edit.php: Dynamic DNS noip-free (): _update() starting. Is the DYNDNS updater broken on dual wan or something. They have been red for a while, but I have VZW static IP addresses, and pay for the DNS service. But the Status column on the Dynamic DNS page says 'disabled', even though I edited and saved the configuration settings, and it didn't complain. I then have a backup internet, Verizon 4G, where every router I log into the DYNDNS is red. services_dyndns_edit.php: Response Header: HTTP/2 200 The DynDNS update log says it's been receiving updates, every 30 minutes, as configured. services_dyndns_edit.php: Response Header: server: nginx services_dyndns_edit.php: Response Header: content-type: text/plain charset=UTF-8 services_dyndns_edit.php: Response Header: cache-control: no-cache services_dyndns_edit.php: Response Header: date: Tue, 08:20:18 GMT services_dyndns_edit.php: Response Header: content-length: 20 services_dyndns_edit.php: Response Header: services_dyndns_edit.php: Dynamic DNS noip-free (): _checkStatus() starting. services_dyndns_edit.php: Dynamic DNS noip-free (): 82.127.34.254 extracted from Check IP Service
![dyn updater says disabled dyn updater says disabled](https://technical-tips.com/assets/images/photos/1559508386.png)
![dyn updater says disabled dyn updater says disabled](https://setuprouter.com/router/engenius/esr9350/dynamic-dns-30295-large.jpg)
services_dyndns_edit.php: phpDynDNS: updating cache file /conf/dyndns_wannoip-free''2.cache: 82.127.34.254 I did find a trace on my remote syslogger : (in reverse order) : /services_dyndns_edit.php: phpDynDNS (): (Success) IP address is current, no update performed. It finished to do "it's thing" and although I was asking for a verbose log, I could not find any info about the activity in the pfSense logs.
![dyn updater says disabled dyn updater says disabled](https://www.giantbomb.com/a/uploads/scale_medium/33/338034/3287109-7037098785-apps.50417.14482439274633098.49370669-3ed1-43f0-8329-43d00fbffe6d.f057575a-07c1-4363-9319-88aa9aa9a3b9.jpg)
If that was so, your update will be considered as not needed and abusive and you might be "punished" - this will produce a fail for sure. Automatically determines which network interface to use. Logs activity to file, displays visual indicators of the Updater status. Works on Windows XP SP3, Windows Vista, Windows Server, Windows 7 and Windows 8. That's why I changed it to 82.127.34.10 up front. Updates your DynDNS hostnames to resolve to your remote IP address. It's IMPORTANT that, when you force an update, the registered A record at no-ip has not your current, actual WAN IP. The A record defaulted to my WAN IP, 82.127.34.254 (please, don't tell anyone) so I changed it to something different : 82.127.34.10Īfter the initial save, I edited the settings, just to apply the "Apply é Force" button.