starred/ddns-updater
1
0
Fork 0
mirror of https://github.com/qdm12/ddns-updater.git synced 2026-08-02 18:48:49 -04:00
Code Issues 312 Packages Projects Releases 10 Wiki Activity

Bug: dynu sais success update but no update done #323

New Issue
Closed
opened 2025-11-20 04:22:43 -05:00 by saavagebueno · 10 comments
saavagebueno commented 2025-11-20 04:22:43 -05:00
Owner
Copy Link

Originally created by @DFlexy on GitHub (Oct 26, 2023).

Good morning
I'm using DynDNS because it's not working and I created an account on dynu.com and duckdns
Only duck's account is working, dyn's account says it has a bad request and dynu.com's account says the update was done, but when checking if any site doesn't work

image

Originally created by @DFlexy on GitHub (Oct 26, 2023). Good morning I'm using DynDNS because it's not working and I created an account on dynu.com and duckdns Only duck's account is working, dyn's account says it has a bad request and dynu.com's account says the update was done, but when checking if any site doesn't work ![image](https://github.com/qdm12/ddns-updater/assets/50220928/4d0ac710-4e17-4703-8874-fda1c0ab841b)
saavagebueno commented 2025-11-20 04:22:44 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Jan 15, 2024):

What's in your container logs?

You could also try running with LOG_LEVEL=debug

@qdm12 commented on GitHub (Jan 15, 2024): What's in your container logs? You could also try running with `LOG_LEVEL=debug`
saavagebueno commented 2025-11-20 04:22:44 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Jan 19, 2024):

The dyndns failure is solved in #401 and the fix is builtin the latest image and future (soon) release image :2.6

@qdm12 commented on GitHub (Jan 19, 2024): The dyndns failure is solved in #401 and the fix is builtin the latest image and future (soon) release image `:2.6`
saavagebueno commented 2025-11-20 04:22:45 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Jan 29, 2024):

Any news on why dynu is giving a false positive for the update??

@qdm12 commented on GitHub (Jan 29, 2024): Any news on why dynu is giving a false positive for the update??
saavagebueno commented 2025-11-20 04:22:45 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Jan 29, 2024):

Closing this due to inactivity, but feel free to comment back with logs and I'll re-open and dig into it. Thanks!

@qdm12 commented on GitHub (Jan 29, 2024): Closing this due to inactivity, but feel free to comment back with logs and I'll re-open and dig into it. Thanks!
saavagebueno commented 2025-11-20 04:22:45 -05:00
Author
Owner
Copy Link

@rcjcarr commented on GitHub (Feb 25, 2024):

Same issue here; web interface reports a successful Dynu DDNS update, but this is not the case. Container log shows:

========================================
========================================
============= ddns-updater =============
========================================
=========== Made with ❤️ by ============
======= https://github.com/qdm12 =======
========================================
========================================
Running version latest built on 2024-02-13T10:44:47.174Z (commit 6a6b1a8)
🔧 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? quentin.mcgaw@gmail.com
💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12
2024-02-25T08:48:24-05:00 INFO Settings summary:
├── HTTP client
|   └── Timeout: 10s
├── Update
|   ├── Period: 5m0s
|   └── Cooldown: 5m0s
├── 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: /updater/data
├── Backup: disabled
└── Logger
    ├── Level: debug
    └── Caller: hidden
2024-02-25T08:48:24-05:00 INFO reading JSON config from file /updater/data/config.json
2024-02-25T08:48:24-05:00 DEBUG config read: {
  "settings": [
    {
      "provider": "dynu",
      "domain": "xxx.ddnsfree.com",
      "host": "@",
      "group": "group",
      "username": "xxxx",
      "password": "xxxxxxxxx",
      "ip_version": "ipv4",
      "ipv6_suffix": "",
      "provider_ip": true
    }
  ]
}
2024-02-25T08:48:24-05:00 INFO Found single setting to update record
2024-02-25T08:48:24-05:00 INFO Reading history from database: domain xxx.ddnsfree.com host @ ipv4
2024-02-25T08:48:24-05:00 DEBUG configured to fetch IP: v4 or v6: false, v4: true, v6: false
2024-02-25T08:48:24-05:00 INFO [backup] disabled
2024-02-25T08:48:24-05:00 INFO [healthcheck server] listening on 127.0.0.1:9999
2024-02-25T08:48:24-05:00 INFO [http server] listening on :8000
2024-02-25T08:48:24-05:00 DEBUG your public IP address are: v4 or v6: invalid IP, v4: 172.83.166.163, v6: invalid IP
2024-02-25T08:48:24-05:00 DEBUG record xxx.ddnsfree.com (ipv4) is within cooldown period of 5m0s, skipping update
2024/02/25 08:52:48 "GET http://192.168.1.51:8004/ HTTP/1.1" from 192.168.1.29:52669 - 200 1698B in 42.021µs
2024/02/25 08:52:48 "GET http://192.168.1.51:8004/favicon.ico HTTP/1.1" from 192.168.1.29:52669 - 404 19B in 6.264µs
2024-02-25T08:53:24-05:00 DEBUG configured to fetch IP: v4 or v6: false, v4: true, v6: false
2024-02-25T08:53:24-05:00 DEBUG your public IP address are: v4 or v6: invalid IP, v4: 172.83.166.163, v6: invalid IP
2024-02-25T08:53:24-05:00 INFO ipv4 address of xxx.ddnsfree.com is 172.83.167.238 and your ipv4 address  is 172.83.166.163
2024-02-25T08:53:24-05:00 INFO Updating record [domain: xxx.com | host: @ | provider: dynu | ip: ipv4] to use 172.83.166.163
2024-02-25T08:53:24-05:00 DEBUG GET https://api.dynu.com/nic/update?hostname=xxx.ddnsfree.com&location=group&password=xxxxxxs&username=xx| headers: User-Agent: DDNS-Updater quentin.mcgaw@gmail.com

Any help appreciated.

@rcjcarr commented on GitHub (Feb 25, 2024): Same issue here; web interface reports a successful Dynu DDNS update, but this is not the case. Container log shows: ``` ======================================== ======================================== ============= ddns-updater ============= ======================================== =========== Made with ❤️ by ============ ======= https://github.com/qdm12 ======= ======================================== ======================================== Running version latest built on 2024-02-13T10:44:47.174Z (commit 6a6b1a8) 🔧 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? quentin.mcgaw@gmail.com 💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12 2024-02-25T08:48:24-05:00 INFO Settings summary: ├── HTTP client | └── Timeout: 10s ├── Update | ├── Period: 5m0s | └── Cooldown: 5m0s ├── 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: /updater/data ├── Backup: disabled └── Logger ├── Level: debug └── Caller: hidden 2024-02-25T08:48:24-05:00 INFO reading JSON config from file /updater/data/config.json 2024-02-25T08:48:24-05:00 DEBUG config read: { "settings": [ { "provider": "dynu", "domain": "xxx.ddnsfree.com", "host": "@", "group": "group", "username": "xxxx", "password": "xxxxxxxxx", "ip_version": "ipv4", "ipv6_suffix": "", "provider_ip": true } ] } 2024-02-25T08:48:24-05:00 INFO Found single setting to update record 2024-02-25T08:48:24-05:00 INFO Reading history from database: domain xxx.ddnsfree.com host @ ipv4 2024-02-25T08:48:24-05:00 DEBUG configured to fetch IP: v4 or v6: false, v4: true, v6: false 2024-02-25T08:48:24-05:00 INFO [backup] disabled 2024-02-25T08:48:24-05:00 INFO [healthcheck server] listening on 127.0.0.1:9999 2024-02-25T08:48:24-05:00 INFO [http server] listening on :8000 2024-02-25T08:48:24-05:00 DEBUG your public IP address are: v4 or v6: invalid IP, v4: 172.83.166.163, v6: invalid IP 2024-02-25T08:48:24-05:00 DEBUG record xxx.ddnsfree.com (ipv4) is within cooldown period of 5m0s, skipping update 2024/02/25 08:52:48 "GET http://192.168.1.51:8004/ HTTP/1.1" from 192.168.1.29:52669 - 200 1698B in 42.021µs 2024/02/25 08:52:48 "GET http://192.168.1.51:8004/favicon.ico HTTP/1.1" from 192.168.1.29:52669 - 404 19B in 6.264µs 2024-02-25T08:53:24-05:00 DEBUG configured to fetch IP: v4 or v6: false, v4: true, v6: false 2024-02-25T08:53:24-05:00 DEBUG your public IP address are: v4 or v6: invalid IP, v4: 172.83.166.163, v6: invalid IP 2024-02-25T08:53:24-05:00 INFO ipv4 address of xxx.ddnsfree.com is 172.83.167.238 and your ipv4 address is 172.83.166.163 2024-02-25T08:53:24-05:00 INFO Updating record [domain: xxx.com | host: @ | provider: dynu | ip: ipv4] to use 172.83.166.163 2024-02-25T08:53:24-05:00 DEBUG GET https://api.dynu.com/nic/update?hostname=xxx.ddnsfree.com&location=group&password=xxxxxxs&username=xx| headers: User-Agent: DDNS-Updater quentin.mcgaw@gmail.com ``` Any help appreciated.
saavagebueno commented 2025-11-20 04:22:45 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Feb 25, 2024):

The body of the http response is nochg (from your logs), so there the updated succeeded and no change was needed I think. Maybe it's due to caching on dns servers and the ttl (could take 1 hour)? What's the value for the A record on the dynu website?

@qdm12 commented on GitHub (Feb 25, 2024): The body of the http response is `nochg` (from your logs), so there the updated succeeded and no change was needed I think. Maybe it's due to caching on dns servers and the ttl (could take 1 hour)? What's the value for the A record on the dynu website?
saavagebueno commented 2025-11-20 04:22:45 -05:00
Author
Owner
Copy Link

@rcjcarr commented on GitHub (Feb 25, 2024):

Hmm, no problem updating with linuxserver/ddclient. I'm running docker in a proxmox lxc container. Would that impact anything?

@rcjcarr commented on GitHub (Feb 25, 2024): Hmm, no problem updating with linuxserver/ddclient. I'm running docker in a proxmox lxc container. Would that impact anything?
saavagebueno commented 2025-11-20 04:22:45 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Feb 25, 2024):

No, but answer the previous question 😉

@qdm12 commented on GitHub (Feb 25, 2024): No, but answer the previous question 😉
saavagebueno commented 2025-11-20 04:22:46 -05:00
Author
Owner
Copy Link

@rcjcarr commented on GitHub (Feb 25, 2024):

Sorry about that; not sure I understand the question. Are you asking for my domain name?

@rcjcarr commented on GitHub (Feb 25, 2024): Sorry about that; not sure I understand the question. Are you asking for my domain name?
saavagebueno commented 2025-11-20 04:22:46 -05:00
Author
Owner
Copy Link

@rcjcarr commented on GitHub (Feb 25, 2024):

TTL is set at 120 on the A record at Dynu.

@rcjcarr commented on GitHub (Feb 25, 2024): TTL is set at 120 on the A record at Dynu.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Category: Config problem 📝
Category: Database 🗃️
Category: Documentation ✒️
Category: Foolproof settings 👼
Category: Good idea 🎯
Category: Healthcheck 🩺
Category: IP fetching 📥
Category: Label missing ❗
Category: Maintenance ⛓️
Category: Motivated! 🙌
Category: New provider 🆕
Category: Provider update ♻️
Category: Shoutrrr 📢
Category: Web UI 🖱️
Category: Wildcard 🃏
Closed: ⚰️ Inactive
Closed: 👥 Duplicate
Closed: 🗑️ Bad issue
Complexity: ☣️ Hard to do
Complexity: 🟩 Easy to do
Priority: 💤 Low priority
Priority: 🚨 Urgent
pull-request
Mirrored from GitHub Pull Request
 Status: 🔒 After next release
Status: 🔴 Blocked
Status: 🗯️ Waiting for feedback
No Label Category: Provider update ♻️ Closed: ⚰️ Inactive Priority: 🚨 Urgent Status: 🗯️ Waiting for feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ddns-updater#323
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?