Post Using location with ddclient
Friday, December 09, 2016 8:46:27 AM

After using Dynu for a while, realized that the DDNS location feature would simplify management of my domain names. By default, ddclient has no support for location, but it can be added with a one-line change. Unfortunately the ddclient source code is pretty ugly with lots of copied/pasted slightly modified functions that all look similar. Use at your own risk, but here is how I modified mine for location support:

#1- Search for: sub nic_dyndns2_update {
(If you don't search on the entire string above, you will end up in the wrong place.)
#2- Search for: my $reply
(This will find the location with the function nic_dyndns2_update)
#3- Insert these lines before the "my $reply" line:
# ddclient hack to support Dynu location based updates
($url =~ /&hostname=[^.&]+&/) && ($url =~ s/&hostname=/&location=/);

In simple terms, if you specify a hostname that does not contain a period (which cannot be legit since its not fully qualified), this hack will rewrite the hostname= to location= allowing Dynu to treat as a location.

In ddclient.conf, you can use something like:, login=, password= location-string

Note there is a quirk with how Dynu handles location-based updates that can cause issues. I had manually set the IP addresses of two of my hosts via the control panel to one of my external servers. I then used the API to change them "back" to my other server via API. The API returned "nochg" (does not require change) even though the current IP addresses were different from what I was passing in the API. Think itsrelated to making both changes from the same IP address. In typical DDNS operation, most updates are in response to an ISP IP address update which appears to work consistently.

Should Dynu wish to investigate, the exact replication steps are:

From IP address H, use the API to update location L to IP address X
good X
From IP address H, use the control panel to update hostnames with location L to address Y
From IP address H, use the API to update location L to IP address X
From IP address H, use the API to update location L to IP address Z

Am guessing the API calls have a caching layer to prevent unneeded updates (very sensible), but seems like a cache key/invalidation issue. Seems like its assuming that all API calls from H for location L are the same (but that is not correct unless myip=H). Probably should be using X/Y/Z (myip) rather than H. If using H is deliberate behavior (because it makes it harder to abuse the service), then should be documented since it has side-effects. Regardless, seems like a control panel update change should invalidate the cache if a location is set for the hostname being updated.

Great service and hope this benefits someone. Thanks.