qdm12 / ddns-updater

Container to update DNS records periodically with WebUI for many DNS providers
https://hub.docker.com/r/qmcgaw/ddns-updater/
MIT License
1.46k stars 146 forks source link

Bug: Ionos wildcard handling #718

Closed Cilenco closed 2 weeks ago

Cilenco commented 1 month ago

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))

dernicc commented 1 month ago

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
qdm12 commented 2 weeks ago

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!)

Cilenco commented 2 weeks ago

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