DYN UPDATER ALTERNATIVE UPDATE

Packages wget or curl not installed to support secure communication. You will find a logfile for every configuration/section.Д¬at /var /log /ddns /myddns_ipv6.log DebuggingД¬heck if your DDNS provider ONLY supports secure requests and enable HTTPS option use_https in your configuration. To view logfile content from LuCI select the Log File Viewer tab of desired configuration/section and press the Read / Reread log file button.ДЇrom console you should change to the ddns log directory, default /var/log/ddns. If the option is defined at config service level, it will be ignored by the /usr/lib/ddns/dynamic_dns_functions.sh script and the log location will be defaulted to /var/log/ddns. This option must be defined in the global section of the /etc/config/ddns file. To achieve this, you need to change the log file location by adding the following line in the global section of /etc/config/ddns: In case your device has enough built in memory or if you are using Extroot, you might want to store the ddns logs persistently. Inside LuCI you could enable logfile in Advanced Settings tab of desired configuration/section.ДЇrom console you need to edit the config file:

Logfiles are automatically truncated to a settable number of lines (default 250 lines). usr /lib /ddns /dynamic_dns_updater.sh myddns 0 & MonitoringДdns-scripts have built-in logfile support. To start your configuration via build in crond use the following entry as command inside crontab configuration (replace myddns with the name of your configuration/section): To guarantee that your configurations only run once not looking for an interface event you need to disable ddns service. The configuration/section configured to run once will stop after successful update. If you set ddns service to enable then all configurations/sections are started during interface ifup. Inside LuCI set Force Interval in Timer Settings tab of your desired configuration or edit /etc/config/ddns on console.

To configure your configuration/section to run once you need to set option force_interval 0.

DYN UPDATER ALTERNATIVE UPDATE

To stop one configuration/section you need to list running ddns processes with:Д®ach configuration/section of ddns-scripts can be configured to run once including retry on error so it is guaranteed that the update is sent to the provider. Sh /usr /lib /ddns /dynamic_dns_functions.sh # note the leading period followed by a space To start all ddns-scripts configurations configured for one interface (the interface name from /etc/config/network, usually 'wan'): usr /lib /ddns /dynamic_dns_updater.sh myddns 0 & To start only one ddns-scripts configuration/section (here myddns): firewall) might be (re-)started via ifup hotplug event!ДЇor INTERFACE, type the specified ddns-scripts interface name (the interface name from /etc/config/network, usually 'wan')ДЄCTION= ifup INTERFACE=wan /sbin /hotplug-call iface Keep in mind that also other service processes (i.e. This will start all enabled ddns configurations/sections monitoring this interface. Users reported timeout problems, use links in the line below (вЂ¦:8245).ДЇrom console command line you could create an ifup hotplug event for the desired network interface. Uci commit ddns # don't forget this, otherwise data not written to configuration file Uci set = set = 'wan' # network interface that should start this configuration/section Uci set _name= '' # only use names listed in /usr/lib/ddns/services # or /usr/lib/ddns/services_ipv6 (since CC 15.05) Other editors as vi needs to be installed separately.ДЄlternatively you can use UCI command line interface. The easiest way to configure ddns-scripts via console is to edit the file /etc/config/ddns directly using build-in vi editor or any other editor you prefer.

Dyn updater alternative