NoIP provider_ip defaults to IPv4 even when setting to IPv6

[NightFurySL2001]

This is just a documentation here to not forget why I wasted months debugging things and thought this wasn't working. In the end: this software was working, the problem is with NoIP.

For noip.com/ddns.net, if you want to update IPv6 only, you must use provider_ip: false. On the provider side, the default is to fetch IPv4 only without updating IPv6.

What had happened:

Config file:

{
  "settings": [
    {
      "provider": "noip",
      "domain": "all.ddnskey.com",
      "host": "@",
      "username": "[redacted]@ddnskey.com",
      "password": "[redacted]",
      "ip_version": "ipv6",
      "provider_ip": true
    }
  ]
}

Debug log:

2024-06-22T16:25:18Z INFO Found single setting to update record
2024-06-22T16:25:18Z INFO Reading history from database: domain all.ddnskey.com host @ ipv6
2024-06-22T16:25:18Z INFO [healthcheck server] health http server listening on 127.0.0.1:9999
2024-06-22T16:25:18Z INFO [http server] http server listening on [::]:8000
2024-06-22T16:25:18Z INFO [backup] disabled
2024-06-22T16:25:18Z DEBUG configured to fetch IP: v4 or v6: false, v4: false, v6: true
2024-06-22T16:25:19Z DEBUG your public IP address are: v4 or v6: invalid IP, v4: invalid IP, v6: 2001:e68::::0
2024-06-22T16:25:19Z INFO ipv6 address of all.ddnskey.com is 2001:e68::::1 and your ipv6 address  is 2001:e68::::0
2024-06-22T16:25:19Z INFO Updating record [domain: all.ddnskey.com | host: @ | provider: noip | ip: ipv6] to use 2001:e68::::0
2024-06-22T16:25:19Z DEBUG GET https://[username]@ddnskey.com:[password]@dynupdate.no-ip.com/nic/update?hostname=all.ddnskey.com | headers: Authorization: Basic [key redacted]; User-Agent: DDNS-Updater [email protected]
2024-06-22T16:25:20Z DEBUG 200 OK | headers: Date: Sat, 22 Jun 2024 16:25:20 GMT; Server: nginx; Content-Type: text/plain; charset=UTF-8; Connection: keep-alive; Cache-Control: no-cache, private | body: nochg 175.142.x.x

[qdm12]

Thank you for reporting this! 💯
I did only change the code in 7ad0d8d so that it 'sneakily' changes use provider ip to false when using ipv6, because it doesn't make any sense anyway. I did think about updating the documentation, then about making ddns-updater return an error if use provider ip is used with ipv6, but I really feel not bothering the user and just "getting shit done" is the best approach 😄
Next time, feel free to open a bug issue since this is border line a bug 😉 Documentation could be updated, but the code can often just be changed to enforce things and remove the need for additional documentation.