nextcloud / nextcloud/nextcloudpi
Add support for dynv6.com dynDNS provider
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.9k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
Problem
The supported dynDNS providers either have an unintuitive interface, or have a freemium model.
Suggestion
This is why I would suggest to support dynv6.com. It's a reputable German dynDNS provider. Also, it is completely free.
Despite the name, you can set up any kind of DNS record, not only AAAA. My main reason to use this provider over others, it has a decluttered and intuitive interface. Also, it is very easy to use your own domain with it. Alternatively, you can choose between 6 different domains provided by them and create as many subdomains as you like.
The provider supports HTTP (REST, DynDNS and Update), SSH and DNS update APIs. (docs/APIs)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's existing dynDNS provider integrations and the dynv6 API documentation linked in the issue. Compare the HTTP, SSH, and DNS update APIs with the project's current provider approach, then verify that dynv6 records can be updated successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100