<ddns-scripts>: <the format of the domain field change>
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Package Name
ddns-scripts
Maintainer
@feckert
OpenWrt Version
master
OpenWrt Target/Subtarget
ubus call system board | jsonfilter -e '@.release.target'
Steps to Reproduce
I encountered an issue regarding the format of the domain field while using ddns-aliyun.
In versions from at least a year ago, setting it to mydomain.xxxx.xxx worked correctly and was consistent with the documentation.
However, in the current version, it only works if I use mydomain@xxxx.xxx. There is no mention of this change in any of the documentation.
Is this a bug, or is it an intended modification to the functionality?
Actual Behaviour
None
Confirmation Checklist
- The package is maintained in this repository.
- I understand that issues related to the base OpenWrt repository or LuCI repository will be closed.
- I am reporting an issue for OpenWrt, not an unsupported fork.
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 inspecting the ddns-scripts package and the ddns-aliyun entry point, then compare how the domain field is parsed with the package documentation. Determine whether the dot-separated and at-sign formats are intended to work; done means the behavior is clarified and the documentation or reported functionality is made consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100