Bug: Dynu: Tool said Success, but IP didn't change on Dynu

[haiheo963]

Hello admin.
When I use this tool to update IP on Dynu, tool return Success or Up-to-date, but the ip didn't update on Dynu

[Debug logs]
╰─❯❯❯ D:\DDNSUpdater\ddns-updater.exe --log-level=DEBUG
========================================
========================================
============= ddns-updater =============
========================================
=========== Made with ❤️ by ============
======= https://github.com/qdm12 =======
========================================
========================================

Running version unknown built on an unknown date (commit unknown)

🔧 Need help? https://github.com/qdm12/ddns-updater/discussions/new
🐛 Bug? https://github.com/qdm12/ddns-updater/issues/new
✨ New feature? https://github.com/qdm12/ddns-updater/issues/new
☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new
💻 Email? [email protected]
💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12
2024-07-16T20:03:37+07:00 INFO Settings summary:
├── HTTP client
|   └── Timeout: 20s
├── Update
|   ├── Period: 2m0s
|   └── Cooldown: 1m0s
├── Public IP fetching
|   ├── HTTP enabled: yes
|   ├── HTTP IP providers
|   |   └── all
|   ├── HTTP IPv4 providers
|   |   └── all
|   ├── HTTP IPv6 providers
|   |   └── all
|   ├── DNS enabled: yes
|   ├── DNS timeout: 3s
|   └── DNS over TLS providers
|       └── all
├── Resolver: use Go default resolver
├── Server
|   ├── Listening address: :8000
|   └── Root URL: /
├── Health
|   └── Server listening address: 127.0.0.1:9999
├── Paths
|   ├── Data directory: ./data
|   └── Config file: data\config.json
├── Backup: disabled
└── Logger
    ├── Level: DEBUG
    └── Caller: hidden
2024-07-16T20:03:37+07:00 INFO reading JSON config from file data\config.json
2024-07-16T20:03:37+07:00 DEBUG config read: {
  "settings": [
    {
      "provider": "dynu",
      "domain": "xxx.giize.com",
      "group": "XX",
      "username": "xxx",
      "password": "xxx",
      "ip_version": "ipv4",
      "ipv6_suffix": "",
      "provider_ip": true
    },
    {
      "provider": "dynu",
      "domain": "xxx.giize.com",
      "group": "XX",
      "username": "xxx",
      "password": "xxx",
      "ip_version": "ipv6",
      "ipv6_suffix": "",
      "provider_ip": true
    }
  ]
}
2024-07-16T20:03:37+07:00 INFO Found 2 settings to update records
2024-07-16T20:03:37+07:00 INFO Reading history from database: domain XXX.giize.com owner @ ipv4
2024-07-16T20:03:37+07:00 INFO Reading history from database: domain XXX.giize.com owner @ ipv6
2024-07-16T20:03:37+07:00 INFO [http server] http server listening on [::]:8000
2024-07-16T20:03:37+07:00 INFO [backup] disabled
2024-07-16T20:03:37+07:00 DEBUG configured to fetch IP: v4 or v6: false, v4: true, v6: true
2024/07/16 20:03:37 "GET http://192.168.1.188:8000/ HTTP/1.1" from 192.168.1.188:58659 - 200 3109B in 501.6µs
2024/07/16 20:03:38 "GET http://192.168.1.188:8000/static/styles.css HTTP/1.1" from 192.168.1.188:58659 - 200 3203B in 29.2496ms
2024-07-16T20:03:38+07:00 DEBUG your public IP address are: v4 or v6: invalid IP, v4: 42.117.104.51, v6: 2405:4802:71ac:6e60:60f3:e697:641e:8f6d
2024-07-16T20:03:38+07:00 INFO ipv4 address of XXX.giize.com is invalid IP and your ipv4 address  is "IP@@"
2024-07-16T20:03:38+07:00 DEBUG ipv6 address of XXX.giize.com is "IP@@", skipping update
2024-07-16T20:03:38+07:00 INFO Updating record [domain: XXX.giize.com | owner: @ | provider: dynu | ip: ipv4] to use "IP@@"
2024-07-16T20:03:38+07:00 DEBUG GET https://api.dynu.com/nic/update?hostname=XXX.giize.com&location=XX&password=xxx&username=xxx | headers: User-Agent: DDNS-Updater [email protected]
2024/07/16 20:03:38 "GET http://192.168.1.188:8000/static/favicon.ico HTTP/1.1" from 192.168.1.188:58659 - 200 15086B in 162µs
2024-07-16T20:03:39+07:00 DEBUG 200 OK | headers: Date: Tue, 16 Jul 2024 13:3:38 GMT; Server: Dynu Web Server; X-Powered-By: Dynu Dynamic DNS Service; Content-Length: 5; Content-Type: text/html; charset=UTF-8 | body: nochg
2024/07/16 20:03:41 "GET http://192.168.1.188:8000/ HTTP/1.1" from 192.168.1.188:58659 - 200 3124B in 0s
2024/07/16 20:03:42 "GET http://192.168.1.188:8000/static/styles.css HTTP/1.1" from 192.168.1.188:58659 - 200 3203B in 0s
2024/07/16 20:03:42 "GET http://192.168.1.188:8000/static/favicon.ico HTTP/1.1" from 192.168.1.188:58659 - 200 15086B in 57.8µs
2024/07/16 20:03:42 "GET http://192.168.1.188:8000/ HTTP/1.1" from 192.168.1.188:58659 - 200 3124B in 248.2µs
2024/07/16 20:03:42 "GET http://192.168.1.188:8000/static/styles.css HTTP/1.1" from 192.168.1.188:58659 - 200 3203B in 0s
2024/07/16 20:03:43 "GET http://192.168.1.188:8000/static/favicon.ico HTTP/1.1" from 192.168.1.188:58659 - 200 15086B in 130µs

[qdm12]

I believe the problem comes from using "provider_ip": true. Since you have a ipv4+6 dual stack, dynu determines your ip address using ipv6, and so it compares it to the ipv6 set which is the same, and thus responds nochg. Basically, as soon as you have ipv6 and want to update ipv4 as well, you should not set "provider_ip": true, for all providers.

Anyway, on top of this workaround mentioned, I changed the program to just NOT use provider_ip at all, since it's kind of useless anyway, in commit 918df24 (latest image and next release v2.8.0).