ddns-scripts: Non functional on DS-Lite with IPv4 only provider
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 22/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- shell
- Domain
- networking
Research direction
Start with the ddns-scripts package and the log lines quoted in the report, which show the network_get_ipaddr6 call and the bind_network option (wan_6_4) being used to pick the address source. Reproduce the case where ip_source/interface is set to wan_6 while bind_network points at the IPv4 WAN, and check how the IPv6 address is determined. Done means the AAAA update works through IPv4 transport on a DS-Lite setup without the address being read from the bind address. Related issues #28413 and #21592 are linked in the report and should be read first.
Written by the indexing model from the issue text.
Description
Package Name
ddns-scripts
Maintainer
feckert
OpenWrt Version
25.12.6
OpenWrt Target/Subtarget
bcm27xx/bcm2711
Steps to Reproduce
- DS-Lite connection
- IPv4 only DNS provider (e.g. DuckDNS)
- Upgrade from 25.12.5 to 25.12.6
Actual Behaviour
Upgraded from 25.12.5 to 25.12.6 and noticed the DDNS scripts to not update the DNS-Record anymore. Investigating this, it seems like an escalation of the problem outlined in #28413 by myself and #21592 from years ago.
This only happens on a DS-Lite connection and supposedly any other IPv4/IPv6 transitioning technology without public IPv4. Here, you need to register AAAA (IPv6) records only. However, some DNS providers do not have a public IPv6 (e.g. DuckDNS is only reachable via IPv4), forcing you to update the AAAA record through an IPv4 connection.
Previously, as ddns-scripts by default bind curl to the interface it reads the IP from, this already failed. It would read the IPv6 and try updating through IPv6 or it would try and use the non-public IPv4 as an A record, which again is not the desired outcome. I used the workaround to manually specify the option bind_network 'wan_6_4' to make curl bind to the IPv4 WAN while using the IPv6 interface to retrieve the address. This no longer works, as even with option interface wan_6 and the aforementioned bind_address, it now tries to determine the IPv6 address from the bind_address, ignoring the actual setting of the ip_source/interface options.
[9 Nov 2026, 11:59:53 CET] user.err: ddns-scripts[339]: duckdns: Can not detect current IP using 'network_get_ipaddr6 wan_6_4' - Error: '1' - TERMINATE
And, still, without using the bind_network option:
[9 Nov 2026, 12:05:46 CET] user.err: ddns-scripts[2846]: duckdns: cURL Error: '28' [9 Nov 2026, 12:05:46 CET] user.warn: ddns-scripts[2846]: duckdns: Transfer failed - retry using IP '2001:XXXX::YYYY:ZZZZ' (the correct IPv6) [9 Nov 2026, 12:05:46 CET] user.err: ddns-scripts[2846]: duckdns: cURL Error: '45' [9 Nov 2026, 12:05:46 CET] user.warn: ddns-scripts[2846]: duckdns: Transfer failed - retry 1/0 in 120 seconds
I hope we can figure out a fix for this as it currently completely locks me out of using ddns-scripts on my connection.
Cheers
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.
Edit: Formatting
- Dominant language
- Makefile
- Stars
- 4.7k
- Forks
- 4k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 251
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from openwrt/packages
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
openwrt/packages#31307 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
openwrt/packages#31306 · 1 comment ·
Maintainers usually reply within 1 day
All issues in openwrt/packages
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
webtorrent/webtorrent#3131 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100