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

Bug: Previous IPs NOT in reverse chronological order #404

New Issue
Closed
opened 2025-11-20 04:23:41 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 04:23:41 -05:00
Owner
Copy Link

Originally created by @petanck on GitHub (May 25, 2024).

The list of previous IP addresses starts with the oldest, then the next oldest...whereas the expectation is that it is in reverse chronological order so that you can see the previous IP address (before the last change) and the one before that.

  1. Is this urgent: No
  2. DNS provider(s) you use: Cloudflare
  3. Program version: v2.6.0 (docker)
  4. What are you using to run the container: docker-compose
  5. Extra information (optional)
    Screenshot 2024-05-25 132701

Here's a redacted copy of my updates.json showing that the previous IP address showing in the webpage are the oldest (from August 2023) not the newest:

updates.json

Originally created by @petanck on GitHub (May 25, 2024). <!-- YOU CAN CHAT THERE EVENTUALLY: https://github.com/qdm12/ddns-updater/discussions --> The list of previous IP addresses starts with the oldest, then the next oldest...whereas the expectation is that it is in reverse chronological order so that you can see the previous IP address (before the last change) and the one before that. 1. Is this urgent: No 2. DNS provider(s) you use: Cloudflare 3. Program version: v2.6.0 (docker) 4. What are you using to run the container: docker-compose 5. Extra information (optional) ![Screenshot 2024-05-25 132701](https://github.com/qdm12/ddns-updater/assets/151444936/a080abf4-e97a-4549-baca-64f122b6565a) Here's a redacted copy of my updates.json showing that the previous IP address showing in the webpage are the oldest (from August 2023) not the newest: [updates.json](https://github.com/qdm12/ddns-updater/files/15443148/updates.json)
saavagebueno commented 2025-11-20 04:23:42 -05:00
Author
Owner
Copy Link

@qdm12 commented on GitHub (Jun 14, 2024):

Indeed, thanks for reporting this! It was silly me who wrongly coded the reversion of IP order, my bad!

@qdm12 commented on GitHub (Jun 14, 2024): Indeed, thanks for reporting this! It was silly me who wrongly coded the reversion of IP order, my bad!
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
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#404
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?