Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: IONOS new wildcard entry instead of updating existing one #934

Open
dernicc opened this issue Feb 6, 2025 · 1 comment
Open

Bug: IONOS new wildcard entry instead of updating existing one #934

dernicc opened this issue Feb 6, 2025 · 1 comment

Comments

@dernicc
Copy link

dernicc commented Feb 6, 2025

TLDR: New A wildcard entry on ionos instead of updating existing one

  1. Is this urgent: No

  2. DNS provider(s) you use: Ionos

  3. Program version:

    Running version latest built on 2024-12-24T09:20:36.130Z (commit 78f3061)

  4. What are you using to run the container: docker-compose

  5. Extra information (optional)

Logs:

2025-02-04T18:12:02Z INFO ipv4 address of domain.com is ***.***.***.103 and your ipv4 address is ***.***.***.211
2025-02-04T18:12:02Z INFO ipv4 address of www.domain.com is ***.***.***.103 and your ipv4 address is ***.***.***.211
2025-02-04T18:12:02Z INFO ipv4 address of any.domain.com is ***.***.***.103 and your ipv4 address is ***.***.***.211
2025-02-04T18:12:02Z INFO Updating record [domain: domain.com | owner: @ | provider: ionos | ip: ipv4] to use ***.***.***.211
2025-02-04T18:12:05Z INFO Updating record [domain: domain.com | owner: www | provider: ionos | ip: ipv4] to use ***.***.***.211
2025-02-04T18:12:05Z INFO Updating record [domain: domain.com | owner: * | provider: ionos | ip: ipv4] to use ***.***.***.211
2025-02-04T18:22:04Z INFO ipv4 address of any.domain.com is ***.***.***.103 and your ipv4 address is ***.***.***.211
2025-02-04T18:22:04Z INFO Updating record [domain: domain.com | owner: * | provider: ionos | ip: ipv4] to use ***.***.***.211
2025-02-04T18:32:02Z INFO ipv4 address of any.domain.com is ***.***.***.103 and your ipv4 address is ***.***.***.211
2025-02-04T18:32:02Z INFO Updating record [domain: domain.com | owner: * | provider: ionos | ip: ipv4] to use ***.***.***.211
2025-02-04T18:42:03Z INFO ipv4 address of any.domain.com is ***.***.***.103 and your ipv4 address is ***.***.***.211
2025-02-04T18:42:03Z INFO Updating record [domain: domain.com | owner: * | provider: ionos | ip: ipv4] to use ***.***.***.211
2025-02-05T15:57:08Z ERROR obtaining ipv4 address: after 3 tries, errors were: dial tcp4 208.67.222.222:853: i/o timeout, Get "https://api.ipify.org": dial tcp: lookup api.ipify.org on 127.0.0.11:53: server misbehaving, dial tcp4 1.1.1.1:853: i/o timeout

Configuration file (remove your credentials!):

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

Host OS:
docker-compose on openmediavault 7 (Sandworm)

@Hokdan
Copy link

Hokdan commented Feb 7, 2025

I recently ran into the same problem and did some debugging on the API Test-Page of IONOS.
DDNS-Updates first does a
GET https://api.hosting.ionos.com/dns/v1/zones to get the ID of the specific domain

The next GET is
GET https://api.hosting.ionos.com/dns/v1/zones/myCrypticID?recordName=any.mydomain.de&recordType=A

I tried this request on the Test-Page and didn't get any answer. So DDNS-Updates thinks it need to put a new entry and does this as intended.
I then tried the same get request with record_Name=*.mydomain.de and got back the IDs of both set IP-Adresses.

I'm not into GO, so I could not find out where to find the code to change the text, but I'm sure somebody else (especially qdm12) can fix it easily.

I did a workaround until this is fixed by adding my needed subdomains in the "host": config line. e.g. "host:": "@,www,nextcloud,*" .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants