API version used with dynu.com

[cross]

Hello. I used inadyn with dynu.com for a long time, but eventually some time ago it stopped working. Looking at updating my router (and inadyn version), it seems unchanged.
This may be a question, rather than a issue to be fixed, but I had suspected inadyn used the legacy (aka v1) API, which dynu notes is no longer supported.

But, I see issue #478 which is only a few months ago, which makes me fear my issue may be human error.

I'm getting a 200 response, with content "badauth". It looks from debug that it's doing HTTP Basic auth, which I'm 90% sure is no longer supported. Right now I'm seeing this in 2.8.1, but I don't think the code used for dynu.com has changed substantially, has it? I can test 2.12, I'll do that to verify.

[cross]

Okay, to confirm, I get the same with 2.12.0. Maybe dynu.com isn't supporting that basic style of login anymore?

@mia0x75 can you comment on whether you're still using dynu.com successfully?

[cross]

I opened a support request with dynu. Their docs still include many statements about the more traditional update methods, and even include a ddclient conf file which also reports an auth failure if I try to use it. So. Updates here welcome, but I think it may be a "they changed something" issue and I'll come back after I hear from them.

[Hobbybyte]

The following configuration works fine with actual API of dynu.com - IPV4 + IPV6

DYNU -- https://dynu.com

custom dynu {
  username = >username<
  password = >md5/sha1 of password<
  hostname = >yourhostname.yourdomain<
  ssl = true
  checkip-ssl = true
  checkip-server = checkip.dynu.com
  ddns-server = api.dynu.com
  ddns-path = "/nic/update?username=%u&password=%p&myip=%i&hostname=%h"
}