Problems when using a custom service about inadyn

[troglobit]

Hi, sorry for the late reply!

First of all, bug reports for distribution packaged versions of software should always go through that distribution. They may have applied patches and/or provide support that we as upstream don't know of.

Now, I am painfully well aware of the limitations of the custom service. From time to time I've considered removing it, because it's very difficult to support. I do not have access to all the worlds different DDNS providers.

In your case I suspect it would be easier to simply write a small plugin for your DDNS provider instead of trying to bend custom to fit your needs.

However, if you (or someone else) have a patch to address the problems you've mentioned above, I'm more than willing to add it to Inadyn. So I'm going to leave this issue open, for anyone to pitch in.

Cheers
/Joachim

[troglobit]

Have looked into this a bit more now.

1. The custom@http_srv_basic_auth is for using HTTP basic authentication, using base64 encoded username:password. We should probably support a custom@http_srv_no_auth ...

2. I will however lax the requirement for always supplying a username/password to custom@, it is then up to the server if it accepts base64 encoded "":""

3. The alias setting is required. It is both used internally for tracking time for update etc. and
   is also what is appended to the HTTP GET URL sent to the server on updates. In your case your could set

   alias myhostname
   server-url /update?domain=my.domain&password=mypassword&host=
   

   Unless myhostname was one of those "random words" you talked about, then you could change the config to this:

     alias my.domain
     server-url /update?password=mypassword&domain=
   

4. In newer versions of Inadyn, newer than what Debian/Ubuntu currently has, the generic plugin (which handles custom@) also looks for the string true.

5. Also, I've never seen <ErrCount>0</ErrCount> reported from any other server, so that is not something I'd expect Inadyn to know about. Again, maybe a dedicated plugin for your DDNS provider is a better option?

[troglobit]

In Inadyn v1.99.14 (just released) there is now support for append-myip, which can be used with custom DDNS providers. See the README, or the man pages, for more info on this, quite handy.

I've also updated the README more about custom DDNS provieders. Hope this helps!

[Jurek-Raben]

There is a spelling error in "http_svr_basic_auth", it needs to be "http_srv_basic_auth" instead. srv vs svr. Since svr looks correct to me, the spelling problem is inside the source?

[troglobit]

@JurekRaben This is an issue closed almost three years ago for a very old version of Inadyn. If your problem pertains to a version packaged by a Linux distribution, I suggest you report it there. Current Inadyn releases have no such mechanism anymore.

[Jurek-Raben]

Well hard to know such differences, if you are not the developer yourself. Would be helpful, if you were writing about these differences in versions available in the readme. Kind of annoying to find proper info in Linux world, if everybody only cares for his/her own microcosmos - not you, I mean in general :)

[troglobit]

@JurekRaben I understand your problem, it's simply just not realistic to document all differences to all previous versions from the current one. All major changes are however denoted in the ChangeLog, which most well-maintained projects should have.