ddns: problem with nslookup
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- shell
- Domain
- networking
Research direction
Start by reading the ddns-scripts package configuration and provider definitions; the issue names no source files or tests. Reproduce the BusyBox nslookup error with the described token-based noip.at URL and check how lookup_host is required before updates. Done means the issue’s questions are resolved with a supported way to send the update, or noip.at is supported without blocking on that lookup.
Written by the indexing model from the issue text.
Description
Package Name
ddns
Maintainer
@feckert @dietersss
OpenWrt Version
25.12.6
OpenWrt Target/Subtarget
mediatek/filogic
Steps to Reproduce
I'm using OpenWrt ddns-scripts version 2.8.4-8 with luci-app-ddns.
My provider, noip.at, uses a simple token-based update URL:
https://noip.at/update/HOSTNAME/TOKEN
The update URL does not require a conventional DDNS username/password protocol. However, the DDNS client insists on resolving lookup_host before sending an update.
My hostname resolves to 127.0.0.1 through public DNS, and the updater repeatedly reports:
ERROR: BusyBox nslookup error: '1'
The update request is never reached. My router also uses a VPN, so the WAN interface and the default route are different.
Actual Behaviour
Could Noip.at please be added to the provider list?
if not, Is there a supported way to configure ddns-scripts to send this custom update request without requiring a successful DNS lookup of the hostname first?
Thank you.
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.
- 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