-
-
Notifications
You must be signed in to change notification settings - Fork 158
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: No-Ip ddnskeys support #712
Comments
Thanks for creating the issue 👍
In that case, wouldn't it be simpler to just update each subdomain in a separate setting block, instead of using |
Thanks for the response. No, I think this is not possible. Excerpt from the no-ip documentation:
|
Is issue in this post somehow related to why Docker gives the status of this container being I'm asking so I don't go ahead and create a issue if the problem is the same I attached my |
I think your health check issue is different from mine. I get a wrong ip reported, because ddns updater cannot know the hostname that is updated and your health check is timed out. |
I see, thank you for pointing that out! so I should go ahead and post my problem as a new issue then i suppose Good luck to! |
TLDR: Name resolution for No-Ip ddnskeys
Logs:
Configuration file
Host OS: Ubuntu 22.04.4
I encountered the following problem: Updating the ip for No-Ip with ddnskey works, but ddns updater cannot verify the updated ip. The reason is that it tries to match the updated ip against the ip of api domain of no-ip. With a ddnskey from no-ip, all domains need to access the same url (all.ddnskey.com) and no-ip is matching the domain to upgrade via the ddnskey (username).
A solution would be to an extra field for no-ip where the actual domain that will be updated can be defined. Right now, ddns updater does not know for which domain the ip address has been updated.
Output of the health check:
Docs for ddnskey at no-ip: https://www.noip.com/support/knowledgebase/how-to-setup-and-use-a-ddns-key
The text was updated successfully, but these errors were encountered: