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: Ionos wildcard handling #399

New Issue
Closed
opened 2025-11-20 04:23:34 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 04:23:34 -05:00
Owner
Copy Link

Originally created by @Cilenco on GitHub (May 13, 2024).

TLDR: Ionos provider creates any AAAA record instead of updating * record

  1. Is this urgent: Yes
  2. DNS provider(s) you use: Ionos
  3. Program version: Running version 2.6.0 built on 2024-02-03T18:53:40.722Z (commit c338c28)
  4. What are you using to run the container: docker-compose
  5. Extra information

ionos bug

Logs:

INFO Updating record [domain: domain.tld | host: @ | provider: ionos | ip: ipv6] to use <ip6-address>
INFO Updating record [domain: domain.tld | host: * | provider: ionos | ip: ipv6] to use <ip6-address>

Configuration file (remove your credentials!):

{
  "settings": [
    {
      "provider": "ionos",
      "domain": "domain.tld",
      "api_key": "...",
      "ip_version": "ipv6",
      "host": "@,*"
    }
  ]
}

Host OS: Raspberry Pi OS (Debian GNU/Linux 12 (bookworm))

Originally created by @Cilenco on GitHub (May 13, 2024). **TLDR**: Ionos provider creates any AAAA record instead of updating * record 1. Is this urgent: Yes 2. DNS provider(s) you use: Ionos 3. Program version: `Running version 2.6.0 built on 2024-02-03T18:53:40.722Z (commit c338c28)` 4. What are you using to run the container: docker-compose 5. Extra information ![ionos bug](https://github.com/qdm12/ddns-updater/assets/4381287/dacf2db8-2bbe-41ed-ae24-62ebe51d104a) Logs: ``` INFO Updating record [domain: domain.tld | host: @ | provider: ionos | ip: ipv6] to use <ip6-address> INFO Updating record [domain: domain.tld | host: * | provider: ionos | ip: ipv6] to use <ip6-address> ``` Configuration file (**remove your credentials!**): ``` { "settings": [ { "provider": "ionos", "domain": "domain.tld", "api_key": "...", "ip_version": "ipv6", "host": "@,*" } ] } ``` Host OS: Raspberry Pi OS (Debian GNU/Linux 12 (bookworm))
saavagebueno commented 2025-11-20 04:23:35 -05:00
Author
Owner
Copy Link

@dernicc commented on GitHub (May 13, 2024):

Same for me and ipv4.

Logs:

2024-05-13T00:04:57Z INFO ipv4 address of any.domain.de is 37.XX.XXX.XX and your ipv4 address  is 37.YY.YY.YY
2024-05-13T00:04:57Z INFO Updating record [domain: domain.de | host: * | provider: ionos | ip: ipv4] to use 37.YY.YY.YY
2024-05-13T00:14:56Z INFO ipv4 address of any.domain.de is 37.XX.XXX.XX and your ipv4 address  is 37.YY.YY.YY
2024-05-13T00:14:56Z INFO Updating record [domain: domain.de | host: * | provider: ionos | ip: ipv4] to use 37.YY.YY.YY
2024-05-13T00:24:57Z INFO obtaining ipv4 address succeeded after 1 failed try
2024-05-13T00:24:57Z INFO ipv4 address of any.domain.de is 37.XX.XXX.XX and your ipv4 address  is 37.YY.YY.YY
2024-05-13T00:24:57Z INFO Updating record [domain: domain.de | host: * | provider: ionos | ip: ipv4] to use 37.YY.YY.YY
2024-05-13T00:44:56Z INFO ipv4 address of any.domain.de is 37.XX.XXX.XX and your ipv4 address  is 37.YY.YY.YY
2024-05-13T00:44:56Z INFO Updating record [domain: domain.de | host: * | provider: ionos | ip: ipv4] to use 37.YY.YY.YY
2024-05-13T00:54:56Z INFO ipv4 address of any.domain.de is 37.XX.XXX.XX and your ipv4 address  is 37.YY.YY.YY
2024-05-13T00:54:56Z INFO Updating record [domain: domain.de | host: * | provider: ionos | ip: ipv4] to use 37.YY.YY.YY
2024-05-13T01:04:56Z INFO ipv4 address of any.domain.de is 37.XX.XXX.XX and your ipv4 address  is 37.YY.YY.YY
2024-05-13T01:04:56Z INFO Updating record [domain: domain.de | host: * | provider: ionos | ip: ipv4] to use 37.YY.YY.YY

Configuration:

{
    "settings": [
      {
        "provider": "ionos",
        "domain": "domain.de",
        "host": "@,www,*",
        "api_key": "api.key",
        "ip_version": "ipv4",
        "ipv6_suffix": ""
      }
    ]
  }

docker-compose.yml:

version: "3.7"
services:
  ddns-updater:
    image: qmcgaw/ddns-updater
    container_name: ddns-updater
    network_mode: bridge
    ports:
      - XXXX:8000/tcp
    volumes:
      - /myvolume/updater/data:/updater/data
    environment:
      - CONFIG=
      - PERIOD=5m
      - UPDATE_COOLDOWN_PERIOD=5m
      - PUBLICIP_FETCHERS=all
      - PUBLICIP_HTTP_PROVIDERS=all
      - PUBLICIPV4_HTTP_PROVIDERS=all
      - PUBLICIPV6_HTTP_PROVIDERS=all
      - PUBLICIP_DNS_PROVIDERS=all
      - PUBLICIP_DNS_TIMEOUT=3s
      - HTTP_TIMEOUT=10s

      # Web UI
      - LISTENING_ADDRESS=:8000
      - ROOT_URL=/

      # Backup
      - BACKUP_PERIOD=0 # 0 to disable
      - BACKUP_DIRECTORY=/updater/data

      # Other
      - LOG_LEVEL=info
      - LOG_CALLER=hidden
      - SHOUTRRR_ADDRESSES=
    restart: always
@dernicc commented on GitHub (May 13, 2024): Same for me and ipv4. Logs: ``` 2024-05-13T00:04:57Z INFO ipv4 address of any.domain.de is 37.XX.XXX.XX and your ipv4 address is 37.YY.YY.YY 2024-05-13T00:04:57Z INFO Updating record [domain: domain.de | host: * | provider: ionos | ip: ipv4] to use 37.YY.YY.YY 2024-05-13T00:14:56Z INFO ipv4 address of any.domain.de is 37.XX.XXX.XX and your ipv4 address is 37.YY.YY.YY 2024-05-13T00:14:56Z INFO Updating record [domain: domain.de | host: * | provider: ionos | ip: ipv4] to use 37.YY.YY.YY 2024-05-13T00:24:57Z INFO obtaining ipv4 address succeeded after 1 failed try 2024-05-13T00:24:57Z INFO ipv4 address of any.domain.de is 37.XX.XXX.XX and your ipv4 address is 37.YY.YY.YY 2024-05-13T00:24:57Z INFO Updating record [domain: domain.de | host: * | provider: ionos | ip: ipv4] to use 37.YY.YY.YY 2024-05-13T00:44:56Z INFO ipv4 address of any.domain.de is 37.XX.XXX.XX and your ipv4 address is 37.YY.YY.YY 2024-05-13T00:44:56Z INFO Updating record [domain: domain.de | host: * | provider: ionos | ip: ipv4] to use 37.YY.YY.YY 2024-05-13T00:54:56Z INFO ipv4 address of any.domain.de is 37.XX.XXX.XX and your ipv4 address is 37.YY.YY.YY 2024-05-13T00:54:56Z INFO Updating record [domain: domain.de | host: * | provider: ionos | ip: ipv4] to use 37.YY.YY.YY 2024-05-13T01:04:56Z INFO ipv4 address of any.domain.de is 37.XX.XXX.XX and your ipv4 address is 37.YY.YY.YY 2024-05-13T01:04:56Z INFO Updating record [domain: domain.de | host: * | provider: ionos | ip: ipv4] to use 37.YY.YY.YY ``` Configuration: ``` { "settings": [ { "provider": "ionos", "domain": "domain.de", "host": "@,www,*", "api_key": "api.key", "ip_version": "ipv4", "ipv6_suffix": "" } ] } ``` docker-compose.yml: ``` version: "3.7" services: ddns-updater: image: qmcgaw/ddns-updater container_name: ddns-updater network_mode: bridge ports: - XXXX:8000/tcp volumes: - /myvolume/updater/data:/updater/data environment: - CONFIG= - PERIOD=5m - UPDATE_COOLDOWN_PERIOD=5m - PUBLICIP_FETCHERS=all - PUBLICIP_HTTP_PROVIDERS=all - PUBLICIPV4_HTTP_PROVIDERS=all - PUBLICIPV6_HTTP_PROVIDERS=all - PUBLICIP_DNS_PROVIDERS=all - PUBLICIP_DNS_TIMEOUT=3s - HTTP_TIMEOUT=10s # Web UI - LISTENING_ADDRESS=:8000 - ROOT_URL=/ # Backup - BACKUP_PERIOD=0 # 0 to disable - BACKUP_DIRECTORY=/updater/data # Other - LOG_LEVEL=info - LOG_CALLER=hidden - SHOUTRRR_ADDRESSES= restart: always ```
saavagebueno commented 2025-11-20 04:23:35 -05:00
Author
Owner
Copy Link

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

aa4a1f3813 likely fixes this, can you pull the latest image docker pull qmcgaw/ddns-updater and try with this image? It was previously setting the name to find/create/update to any.domain.de instead of the now-fixed *.domain.de, my bad!

If it still doesn't work, can you share what logs you get with the LOG_LEVEL=debug set? (remove your credentials!)

@qdm12 commented on GitHub (Jun 14, 2024): aa4a1f381300fcba33d23b2e2e0bde3fcfb0c349 likely fixes this, can you pull the latest image `docker pull qmcgaw/ddns-updater` and try with this image? It was previously setting the name to find/create/update to `any.domain.de` instead of the now-fixed `*.domain.de`, my bad! If it still doesn't work, can you share what logs you get with the `LOG_LEVEL=debug` set? (remove your credentials!)
saavagebueno commented 2025-11-20 04:23:35 -05:00
Author
Owner
Copy Link

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

Yes it does work now with the latest image. Thank you for the fix!

@Cilenco commented on GitHub (Jun 14, 2024): Yes it does work now with the latest image. Thank you for the fix!
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 ♻️ 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#399
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?