#18 0.28.06 doesn't seem to be contacting the server.

[Neil Townsend]

Some issue getting latest code to work. It is configured purely using command line options by a start up script:

#./rc_inadyn-mt start
inadyn-mt started succesfully. (--background --svr_add_cfg /usr/etc/inadyn-mt/extra/servers_additional.cfg --dyndns_system default@dnsomatic.com --alias all.dnsomatic.com --username xxxxx@xxxx --password xxxxxxxxxxx --log_file /var/log/inadyn-mt.log)

However, the log shows:

# cat /var/log/inadyn-mt.log
Fri Jan  2 00:12:19 1970: S:INADYN: Started 'inadyn-mt version 02.28.06' - dynamic DNS updater.
Fri Jan  2 00:12:19 1970: E:CACHE_LIST Failed opening cache file in ip_cache_list_read...
Fri Jan  2 00:12:19 1970: W:DYNDNS: Error 'RC_ERROR' (0x1) when talking to IP server

And it doesn't seem to be doing some updating stuff. This is with 02.28.06; 02.28.04 looked like it worked (it got to authentication failure error messages, at any rate, but I hadn't tested it beyond that.

DNS is working:

# ping updates.dnsomatic.com
PING updates.dnsomatic.com (67.215.92.215): 56 data bytes
64 bytes from 67.215.92.215: seq=0 ttl=57 time=148.100 ms
64 bytes from 67.215.92.215: seq=1 ttl=57 time=148.490 ms
64 bytes from 67.215.92.215: seq=2 ttl=57 time=149.836 ms

[Bryan Hoover]

Hi Neil,

default@dnsomatic.com tested fine over here.

You may be having trouble with write permissions with your cache file - use --cache_dir <file name> to put in a directory for which you have permissions.

Also, it may be ip server, checkip.dyndns.org is timing out - try another one, using --ip_server_name <server name url>, e.g., --ip_server_name ip6.me /. If you're updating ipv4, using ip6.me, you'll need to indicate ip type in --alias parameters (ip4 as first parameter after alias name to --alias option).

Other than that, this may be an OS forum question.

[Neil Townsend]

Hi Bryan,

Thanks for the tip about chache, cleaned that one up, however, still the same failure method. However, leave it with me as I will do some route checking as I am working on a router and there may be routing issues hiding away. I'll get back with a confirm or deny once I've done a few more experiments, may take a few days though.