The DDNS service freedns.afraid.org has a unique identification system. Instead of a username and a password, a hash is attached to the domain name. This looks like -a hostname,LongHashHere on the command line. This worked with previous versions of Freenas. 9.3 now splits by , and doesn't provide any way to escape this, so now freenas tries to update two hostnames of which the first is missing the hash and the second is a non-existing hostname, the hash.
Proposed potential solutions would be to add special handling of , to the afraid driver, to use a different separator (space?) to hostnames or to allow escaping.
#10 Updated by Gerhard Röthlin over 5 years ago
bitsandnumbers - wrote:
Well, what can we do until something is done for a future update ? It's kind of annoying that this feature broke with 9.3 while it was working well with latest 9.2 ! Is Mig Ponce's solution a good workaround ?
It doesn't work. The parameters freenas gives to inadyn-mt are incorrect, so no matter how often it is restarted it will not work. My workaround for now is to just update the IP via a cronjob in a jail, and ignore the non-working freenas native service.
#11 Updated by Erin Clark over 5 years ago
- Status changed from Screened to Closed: Duplicate
- Seen in changed from to 9.3-STABLE-201505040117
I have submitted a fix to nightlies as per ticket #8309 that uses # as the delimiter for the afraid.org hash, please follow that ticket and test the nightlies to see if it is not broken