Dynu Bad authentication

[flixxx]

Trying to setup ddns-updater with my provider dynu
logs pulls the right info (current ip, ip logged on their site, domain, etc..)
when it comes time to update it, the following error;
ERROR bad authentication

I tried using my password, ip updater password, md5 hashed password.

[flixxx]

I've been messing around, tested dynu's api and my information works properly. I believe ddns-updater may not be sending the right formatting.
how can we check what it sends to dynu? Is there a verbose log available.

[qdm12]

Try LOG_LEVEL=debug it should log all requests and responses

[qdm12]

Hello, did you have time to debug it? Thanks!

[JackTalisker]

I have the same problem.
Tried both user and email address as username.
The debug log shows the following:

2022/12/03 14:11:56 INFO Updating record [domain: MYDOMAIN.com | host: MYHOST | provider: dynu | ip: ipv4] to use 123.191.135.321
2022/12/03 14:11:56 DEBUG GET https://api.dynu.com/nic/update?alias=MYALIAS&hostname=MYHOSTNAME.com&location=&password=MYPASSWORD&username=MYUSERNAME%40gmail.com | headers: User-Agent: DDNS-Updater [email protected]
2022/12/03 14:11:59 DEBUG 200 OK | headers: Date: Sat, 03 Dec 2022 13:11:59 GMT; Server: Dynu Web Server; X-Powered-By: Dynu Dynamic DNS Service; Content-Length: 7; Content-Type: text/html; charset=UTF-8 | body: badauth
2022/12/03 14:11:59 ERROR bad authentication

[JackTalisker]

I solved this way:
my old config was

    {
      "provider": "dynu",
      "domain": "mydomain.com",
      "host": "myhost",
      "username": "myusername",
      "password": "mypassword",
      "ip_version": "ipv4",
      "provider_ip": true
    }

I changed to:

    {
      "provider": "dynu",
      "domain": "myhost.mydomain.com",
      "host": "@",
      "username": "myusername",
      "password": "mypassword",
      "ip_version": "ipv4",
      "provider_ip": true
    }

now it works but I suppose it's only a workaround (maybe the problem is the "alias" handling?)

[qdm12]

Awesome that helped quite a bit. Also sorry for the mega delay.

[qdm12]

Fixed in 83a9a2d

[qdm12]

Correct me if I'm wrong:

• update kato.ext.vespian.net: set hostname to vespian.net + alias to kato.ext
• update ext.vespian.net: set hostname to ext.vespian.net, do not set alias
• update vespian.net: set hostname to vespian.net, do not set alias

I would prefer to code these instead of documenting this strange API behavior ideally 😉

[cross]

I am getting here while searching for similar problems with another ddns updater with dynu.com. If I submit hostname=host.domain.com, given that the "DDNS Domain" I have listed with dynu.com is "domain.com", it will respond "badauth".
If I send hostname=domain.com&alias=host it will successfully set the host A record inside of domain.com to the specified address. As noted by @vespian , this would have been the behavior before the change suggested by @JackTalisker .
Jack, what is the domain listed in the Dynu control panel table for you? Is it "mydomain.com", or "myhost.mydomain.com" ?

[qdm12]

@JackTalisker (gentle reminder 😉)

[JackTalisker]

Here is my control panel. How can I help?

[cross]

I was describing the previous page, but I think but I think the link there opens the above page, and the information is what you masked in the upper left.
I don't need to know the exact string there, but I wanted to know if that is the exact string you are setting an address for. In my case, that string there (the domain) is "distal.com", and the names I want to set are inside of it, in the DNS Records link on the right hand side of the DDNS control panel.
Does the question make sense? Is the address you're setting with ddns-updater the same as the string there at the top, or a FQDN a level under that?

[JackTalisker]

Here is my DNS Records page

[cross]

Thanks, Jack. That confirms my suspicion, that you are setting the address of the primary "domain" you have set up with dynu. You have only the root and wildcard records beneath it, both set to the same value (I presume).
So, in that case, hostname is to be used, and apparently it needs to be without an alias ? Responding to @vespian comment, Jack was in fact after the root of the domain, not a subhost.
So we need the hostname/alias syntax when the root domain dynu knows is not the same as the address being set. When you are updating the domain itself, you can update the hostname itself. (and Jack has shown that an "@" as alias works, but is not needed and possibly confusing?)
IMO, @JackTalisker 's original reconfiguration "workaround" is actually correct. It's just confusing given the keys in config. He doesn't want to set the hostname, he wants to set the root domain. That "domain" is just also being used as a hostname.
In response to @qdm12 comment, "it depends on what you have registered at dynu". I am comfortable with "domain" needing to be what's registered, and if you need a member of that domain set, rather than the domain itself, you specify that as a "hostname" parameter. It just is confusing if you have registered a "domain" that in your own opinion is a hostname.