Dynamic DNS Service configured for freedns.afraid.org tries tup date dyndns instead
Just what it says on the tin. If you configure the Dynamic DNS service for freedns.afraid.org it will try to update dyndns.com instead. Apparently this has been broken for a while but no one has officially opened a ticket to have it fixed. See this thread: https://forums.freenas.org/index.php?threads/freedns-afraid-ddns-help.18944/.
#3 Updated by Ian Cartwright almost 6 years ago
I just want to make sure I understand the behavior of inadyn-mt in FreeNAS. My understanding from the man page is that as long as the provider is specified, inadyn-mt will use the default update server for that provider. I have confirmed this is true for some of the providers (easydns and Hurricane Electric). However, what I understand from you is that that even though there is a drop down list to choose the Dynamic DNS provider, that the provider's update server must still be specified? This doesn't seem to match the behavior for EasyDNS and Hurricane Electric. I think that there is a bug such that when freedns.afraid.org is chosen from he drop down, the appropriate command line option is not set which causes inadyn-mt to fall back to its default behavior, which is to contact DynDNS.
#5 Updated by Ian Cartwright almost 6 years ago
My source of information is the man page for inadyn-mt and tcpdump on my FreeNAS server. According to the man page, it is sufficient to specify the Dynamic DNS provider. I confirmed this for EasyDNS and Hurricane Electric via tcpdump.
From the man page (http://manned.org/inadyn-mt.8):
An optional DNS service. For
the acceptable services are one of email@example.com,
firstname.lastname@example.org or email@example.com.
There is only one acceptable service for
http://freedns.afraid.org, which is firstname.lastname@example.org.
Other services are: email@example.com, firstname.lastname@example.org,
email@example.com, firstname.lastname@example.org, email@example.com,
firstname.lastname@example.org, email@example.com, firstname.lastname@example.org,
email@example.com, firstname.lastname@example.org, email@example.com,
firstname.lastname@example.org, custom@http_svr_basic_auth._ The default
service is email@example.com, which is believed to be used by most
users, at least initially.
The server that receives the update DNS requests. When no proxy is
specified it is sufficient to set the dyndns_system so that the
default servers will be taken. The option is useful for generic
DynDNS services that support HTTP update.
-u username -p password -a my.registered.name
--username test --password test --update_period 60000 --alias
test.homeip.net --alias my.second.domain
u test -p test --update_period 60000 --alias
inarcis.homeip.net --alias my.second.domain --log_file inadyn
--dyndns_system firstname.lastname@example.org -a
--update_period 60000 --alias test.homeip.net,hash_for_host1 -a
my.second.domain,hash2 --dyndns_system email@example.com
#8 Updated by Ian Cartwright almost 6 years ago
I'm not looking at the config file at all. I'm using the FreeNAS GUI and not getting the expected results. Are you saying that the GUI generates the config file properly and that inadyn-mt has a bug where it doesn't follow the config file when it comes to freedns.afraid.org?
#11 Updated by Ian Cartwright almost 6 years ago
Well, I figured it out. It looks like freedns.afraid.org is "special" and doesn't take the "standard" fields presented in the GUI. I can document this if desired. I definitely wouldn't say that this "Behaves correctly" using the FreeNAS GUI and documentation. Maybe removing freedns.afraid.org from the drop down list would be an alternative.
#14 Updated by Ian Cartwright almost 6 years ago
Here's where I spelled out what I did to make it work: https://forums.freenas.org/index.php?threads/dynamic-dns-and-freeedns-afraid-org.24455/#post-151746
See attachment for it looks like in the GUI (note: not my actual hashes).