Bug: OVH ZoneDNS is not working #117

Closed
opened 2025-11-20 04:20:28 -05:00 by saavagebueno · 7 comments
Owner

Originally created by @fallenczar on GitHub (May 18, 2021).

Originally assigned to: @qdm12 on GitHub.

TLDR: ZONEDNS information provided as per sample config.json, however logs show that the program is expecting "username" and "password"

  1. Is this urgent: Yes

  2. DNS provider(s) you use: OVH

  3. Program version: commit 864a696

    Running version latest built on 2020-03-13T01:30:06Z (commit d0f678c)

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

  5. Extra information (optional)

Logs:


Configuration file (remove your credentials!):

{
  "settings": [
    {
      "provider": "ovh",
      "domain": "example.ovh",
      "host": "@",
      "username": "example.ovh-test", # added as per error log
      "password": "12345678", # added as per error log
      "api_endpoint": "ovh-eu",
      "app_key": "****",
      "app_secret": "****",
      "consumer_key": "****",
      "ip_version": "ipv4",
      "provider_ip": true
    }
  ]
}

Host OS:OMV - docker

Originally created by @fallenczar on GitHub (May 18, 2021). Originally assigned to: @qdm12 on GitHub. <!-- YOU CAN CHAT THERE EVENTUALLY: https://github.com/qdm12/ddns-updater/discussions --> **TLDR**: ZONEDNS information provided as per sample config.json, however logs show that the program is expecting "username" and "password" 1. Is this urgent: Yes 2. DNS provider(s) you use: OVH 3. Program version: commit 864a696 <!-- See the line at the top of your logs --> `Running version latest built on 2020-03-13T01:30:06Z (commit d0f678c)` 4. What are you using to run the container: docker-compose 5. Extra information (optional) Logs: ```log ``` Configuration file (**remove your credentials!**): ```json { "settings": [ { "provider": "ovh", "domain": "example.ovh", "host": "@", "username": "example.ovh-test", # added as per error log "password": "12345678", # added as per error log "api_endpoint": "ovh-eu", "app_key": "****", "app_secret": "****", "consumer_key": "****", "ip_version": "ipv4", "provider_ip": true } ] } ``` Host OS:OMV - docker
Author
Owner

@fredericrous commented on GitHub (May 18, 2021):

the example is not perfectly clear but the documentation is.
Basically either you use DynHost (aka dynamic) or ZoneDNS (aka api)

example for the zonedns mode:

        {
            "provider": "ovh",
            "domain": "myserver.tld",
            "host": "@",
            "mode": "api",
            "app_key": "some-api-key",
            "app_secret": "some-app-secret",
            "consumer_key": "some-consumer-key"
        }
@fredericrous commented on GitHub (May 18, 2021): the example is not perfectly clear but the documentation is. Basically either you use DynHost (aka `dynamic`) or ZoneDNS (aka `api`) example for the zonedns mode: ``` { "provider": "ovh", "domain": "myserver.tld", "host": "@", "mode": "api", "app_key": "some-api-key", "app_secret": "some-app-secret", "consumer_key": "some-consumer-key" } ```
Author
Owner

@qdm12 commented on GitHub (Jun 7, 2021):

Hey guys, I just pushed 276c1c02fd which removes the dependency on OVH's go library, can you try pulling :latest and see if it works using the zoneDNS (API)? If it doesn't work, I made a release image tag v2.3.0 just before changing this, so you can use that to fallback. Thanks!

Also I'm updating the documentation now to close this issue.

@qdm12 commented on GitHub (Jun 7, 2021): Hey guys, I just pushed 276c1c02fdd44d8ea9d2e78f12a17c33e4ab7da2 which removes the dependency on OVH's go library, can you try pulling `:latest` and see if it works using the zoneDNS (API)? If it doesn't work, I made a release image tag `v2.3.0` just before changing this, so you can use that to fallback. Thanks! Also I'm updating the documentation now to close this issue.
Author
Owner

@fredericrous commented on GitHub (Jun 27, 2021):

I saw a weird logging error. I was getting 2021/06/28 02:32:46 ERROR /updater/data/updates.json validation error: IP 1 of 1 is empty for record {"domain":"mydomain.tld","host":"@","ips":[{"ip":"","time":"2021-06-12T19:47:48.567727675Z"}]}

I removed the updates.json file and was still getting the same issue. I then decided to remove the providers one by one to try to isolate the issue. I removed the OVH ones, then I put them back and the error doesn't appear anymore... 🤦

@fredericrous commented on GitHub (Jun 27, 2021): I saw a weird logging error. I was getting ` 2021/06/28 02:32:46 ERROR /updater/data/updates.json validation error: IP 1 of 1 is empty for record {"domain":"mydomain.tld","host":"@","ips":[{"ip":"","time":"2021-06-12T19:47:48.567727675Z"}]}` I removed the updates.json file and was still getting the same issue. I then decided to remove the providers one by one to try to isolate the issue. I removed the OVH ones, then I put them back and the error doesn't appear anymore... 🤦
Author
Owner

@qdm12 commented on GitHub (Jun 28, 2021):

Thanks for letting me know! Were these using the Zone API? The only line I see is this one where we return the IP address given to do the update as the new IP, so I don't really see why it would be set to an empty string, strange 🤔 I'll dig more later.

@qdm12 commented on GitHub (Jun 28, 2021): Thanks for letting me know! Were these using the Zone API? The only line I see is [this one](https://github.com/qdm12/ddns-updater/blob/master/internal/settings/providers/ovh/provider.go#L231) where we return the IP address given to do the update as the new IP, so I don't really see why it would be set to an empty string, strange 🤔 I'll dig more later.
Author
Owner

@fredericrous commented on GitHub (Jul 8, 2021):

yes, it was Zone API

{
    "settings": [
        {
            "provider": "ovh",
            "domain": "domain.tld",
            "host": "@",
            "mode": "api",
            "app_key": "XXX",
            "app_secret": "XXX",
            "consumer_key": "XXX"
        },
        {
            "provider": "ovh",
            "domain": "domain.tld",
            "host": "*",
            "mode": "api",
            "app_key": "XXX",
            "app_secret": "XXX",
            "consumer_key": "XXXX"
        },
    ]
}
@fredericrous commented on GitHub (Jul 8, 2021): yes, it was Zone API ``` { "settings": [ { "provider": "ovh", "domain": "domain.tld", "host": "@", "mode": "api", "app_key": "XXX", "app_secret": "XXX", "consumer_key": "XXX" }, { "provider": "ovh", "domain": "domain.tld", "host": "*", "mode": "api", "app_key": "XXX", "app_secret": "XXX", "consumer_key": "XXXX" }, ] } ```
Author
Owner

@qdm12 commented on GitHub (Jan 21, 2022):

Closing this due to inactivity. Feel free to comment if it's still unresolved.

@qdm12 commented on GitHub (Jan 21, 2022): Closing this due to inactivity. Feel free to comment if it's still unresolved.
Author
Owner

@silkyclouds commented on GitHub (Mar 14, 2023):

hi gents, I've followed the link you provide to create an app + api keys. But I end up with this :

image

question is, where can I find my customer key ?

thanks !

@silkyclouds commented on GitHub (Mar 14, 2023): hi gents, I've followed the link you provide to create an app + api keys. But I end up with this : <img width="528" alt="image" src="https://user-images.githubusercontent.com/23377067/224980523-e5597fbc-f6b7-4d42-8b02-b08258f0a9c1.png"> question is, where can I find my customer key ? thanks !
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ddns-updater#117