<feed xmlns='http://www.w3.org/2005/Atom'>
<title>packages/net/ddns-scripts, branch master</title>
<subtitle>Mirror of packages feed</subtitle>
<id>https://git-03.infra.openwrt.org/feed/packages/atom?h=master</id>
<link rel='self' href='https://git-03.infra.openwrt.org/feed/packages/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/feed/packages/'/>
<updated>2026-11-17T06:46:31Z</updated>
<entry>
<title>ddns-scripts: add support for query type in busybox nslookup</title>
<updated>2026-11-17T06:46:31Z</updated>
<author>
<name>Jorge Gallegos</name>
</author>
<published>2026-06-10T17:33:34Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/feed/packages/commit/?id=80980cdb5d5c3dca95cba022664d8bc866ad49ec'/>
<id>urn:sha1:80980cdb5d5c3dca95cba022664d8bc866ad49ec</id>
<content type='text'>
Busybox's nslookup supports query type since:

    commit 4b6091f92c1c5abfe4597af4f3f6fa266ac46a5a
    Author: Denys Vlasenko &lt;vda.linux@googlemail.com&gt;
    Date:   Sun Apr 15 12:57:32 2018 +0200

https://github.com/vda-linux/busybox_mirror/commit/4b6091f92c1c5abfe4597af4f3f6fa266ac46a5a

Signed-off-by: Jorge Gallegos &lt;kad@blegh.net&gt;
</content>
</entry>
<entry>
<title>ddns-scripts: add DNSimple DNS provider and bump to v2.8.6</title>
<updated>2026-11-17T06:46:31Z</updated>
<author>
<name>Jorge Gallegos</name>
</author>
<published>2026-06-09T19:29:45Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/feed/packages/commit/?id=cff8bc38b5b611309cddc3d78561ed3c6ab0a7b8'/>
<id>urn:sha1:cff8bc38b5b611309cddc3d78561ed3c6ab0a7b8</id>
<content type='text'>
Add DDNS update support for DNSimple DNS via their REST API.
Authentication is performed via API Token.

Will attempt to create a new or edit an existing A or AAAA record for the
given lookup host and domain. "password" configuration should be set to
DNSimple API token. "username" should be set to the DNSimple account ID.
"domain" should be set to the DNSimple zone. Optionally, "param_opt" can
be set to an existing DNSimple record.

Based it off the porkbun script, as it behaves very similar.

Signed-off-by: Jorge Gallegos &lt;kad@blegh.net&gt;
</content>
</entry>
<entry>
<title>ddns-scripts: remove cnkuai.cn</title>
<updated>2026-11-12T14:36:03Z</updated>
<author>
<name>Josef Schlehofer</name>
</author>
<published>2026-11-11T11:37:40Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/feed/packages/commit/?id=10460f5df7f36b15609dd5775e1fa91a2326dbd4'/>
<id>urn:sha1:10460f5df7f36b15609dd5775e1fa91a2326dbd4</id>
<content type='text'>
The cnkuai.cn update script logs in to the cp.cnkuai.cn control panel
and reads the login captcha by piping it through gif2rgb.

This no longer works. Every plain HTTP request to cp.cnkuai.cn gets a
308 redirect to https://cp.cnkuai.cn without the original path. The
script calls curl without following redirects, so gif2rgb receives the
redirect page instead of the captcha and the update fails at the first
request. Moving the URLs to HTTPS is not enough either. The captcha is
now a 72x18 BMP image, gif2rgb rejects it with "Data is not in GIF
format", and the decoder in the script expects a 48 pixel wide GIF.

Fixing this needs a new captcha decoder and a cnkuai.cn account to test
it with. Remove the ddns-scripts-cnkuai package, its update script and
the provider definition.

Signed-off-by: Josef Schlehofer &lt;pepe.schlehofer@gmail.com&gt;
</content>
</entry>
<entry>
<title>ddns-scripts: apply HTTPS settings to https:// URLs</title>
<updated>2026-11-12T14:35:22Z</updated>
<author>
<name>Josef Schlehofer</name>
</author>
<published>2026-11-11T12:40:42Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/feed/packages/commit/?id=9ae6abf62ac6b6bede554161f5276f45dcee7013'/>
<id>urn:sha1:9ae6abf62ac6b6bede554161f5276f45dcee7013</id>
<content type='text'>
do_transfer() applies the cacert option and checks that the transfer
program supports HTTPS only when use_https is enabled. Many provider
definitions use https:// update URLs, and a custom update_url or ip_url
can do the same. With use_https disabled, such a transfer ignores
cacert, including IGNORE. On a device without HTTPS support the
transfer is still attempted and retried, although it cannot succeed.

Treat a transfer as HTTPS when use_https is enabled or the URL starts
with https://. Without HTTPS support in uclient-fetch, curl or BusyBox
wget, the update now stops with the matching error message, as it
already does with use_https enabled. A cacert value left in a
hand-written configuration with use_https disabled now applies to
https:// URLs. LuCI removes cacert on save when use_https is disabled.

Signed-off-by: Josef Schlehofer &lt;pepe.schlehofer@gmail.com&gt;
</content>
</entry>
<entry>
<title>ddns-scripts: use HTTPS for providers that support it</title>
<updated>2026-11-11T13:44:22Z</updated>
<author>
<name>Josef Schlehofer</name>
</author>
<published>2026-11-11T09:50:56Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/feed/packages/commit/?id=f06a3475a3db936613ef51bdf8ef8f0e8cac9835'/>
<id>urn:sha1:f06a3475a3db936613ef51bdf8ef8f0e8cac9835</id>
<content type='text'>
These providers still send the username, password or token over plain
HTTP, although their update endpoints answer the same way over HTTPS:

all-inkl.com, changeip.com, dnsever.com, dnsexit.com, dnshome.de,
dnsmadeeasy.com, do.de, dondominio.com, duckdns.org, dy.fi, dyn.com,
dyndns.it, dyndns.org, dynu.com, dynv6.com, easydns.com, goip.de,
inwx.de, joker.com, loopia.se, mydns.jp, myonlineportal.net,
mythic-beasts.com, namecheap.com, no-ip.pl, nsupdate.info, oray.com,
schokokeks.org, selfhost.de, strato.com and zoneedit.com

Switch their update URLs to HTTPS. 3322.org, ddo.jp and dhis.org stay
on HTTP because they have no HTTPS update endpoint. duiadns.net stays
on HTTP because it answers every request with HTTP 500.

Signed-off-by: Josef Schlehofer &lt;pepe.schlehofer@gmail.com&gt;
</content>
</entry>
<entry>
<title>ddns-scripts: use HTTPS for providers that redirect to it</title>
<updated>2026-11-11T13:44:22Z</updated>
<author>
<name>Josef Schlehofer</name>
</author>
<published>2026-11-11T08:39:18Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/feed/packages/commit/?id=ff2d5594a609e7317367abf7dfd7341dbf330b43'/>
<id>urn:sha1:ff2d5594a609e7317367abf7dfd7341dbf330b43</id>
<content type='text'>
core-networks.de, dnsomatic.com, ipv64.net, opendns.com, regfish.de and
udmedia.de answer the HTTP update URL with a redirect to HTTPS. curl is
called without --location, so with use_curl enabled the update fails.
udmedia.de also fails with GNU Wget and uclient-fetch after the
redirect, and with every tool the first request goes over plain HTTP.

Use the HTTPS URLs directly.

Signed-off-by: Josef Schlehofer &lt;pepe.schlehofer@gmail.com&gt;
</content>
</entry>
<entry>
<title>ddns-scripts: switch simply.com to ddns.simply.com</title>
<updated>2026-11-11T11:32:52Z</updated>
<author>
<name>Tom Sommer</name>
</author>
<published>2026-10-23T10:34:30Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/feed/packages/commit/?id=9273f21834bd824d6a462a2fe9cf101075137a9f'/>
<id>urn:sha1:9273f21834bd824d6a462a2fe9cf101075137a9f</id>
<content type='text'>
The api.simply.com/2/ddns/ endpoint is deprecated. Use the DynDNS2
service at ddns.simply.com/nic/update instead. It takes the same
hostname and myip parameters, the API key as password and answers with
the usual dyndns2 status codes.

The new service only updates existing records. The A/AAAA record must
already exist in the DNS zone, otherwise the answer is nohost.

Bump PKG_RELEASE.

Signed-off-by: Tom Sommer &lt;mail@tomsommer.dk&gt;
</content>
</entry>
<entry>
<title>ddns-scripts: update to 2.8.5</title>
<updated>2026-11-10T07:40:13Z</updated>
<author>
<name>Andy Chiang</name>
</author>
<published>2026-11-07T04:20:57Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/feed/packages/commit/?id=12ec335dae2fcfb84c5d33a5bfddfe84e10dc06d'/>
<id>urn:sha1:12ec335dae2fcfb84c5d33a5bfddfe84e10dc06d</id>
<content type='text'>
Bump PKG_VERSION for the ddns-scripts changes and reset PKG_RELEASE to
1 as requested.

Signed-off-by: Andy Chiang &lt;AndyChiang_git@outlook.com&gt;
</content>
</entry>
<entry>
<title>ddns-scripts: use retry interval on error 127</title>
<updated>2026-11-10T07:40:13Z</updated>
<author>
<name>Andy Chiang</name>
</author>
<published>2026-11-07T03:58:43Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/feed/packages/commit/?id=3b8bb883c2b4980b06e4bd220d572ae7e6f80f42'/>
<id>urn:sha1:3b8bb883c2b4980b06e4bd220d572ae7e6f80f42</id>
<content type='text'>
`send_update()` returns `127` when the IP to be sent is private, ULA
or otherwise invalid (and "allow non-public IP" is disabled). In this
case nothing is sent to the DDNS provider.

This can happen right after boot when the interface used to obtain the
IP address (e.g. `br-lan`) only has a ULA address yet, because the GUA
(e.g. from prefix delegation) has not been assigned. Currently the
updater then waits a full `Check Interval` (10 minutes by default)
before trying again.

Since no request was sent to the provider, retrying early is safe and
does not risk the rate limiting that the `Check Interval` is meant to
prevent. Use the `Retry Interval` when `send_update()` returns `127`,
and keep using the `Check Interval` for all other cases.

Signed-off-by: Andy Chiang &lt;AndyChiang_git@outlook.com&gt;
</content>
</entry>
<entry>
<title>ddns-scripts: fix debug log for interface IP</title>
<updated>2026-11-10T07:40:13Z</updated>
<author>
<name>Andy Chiang</name>
</author>
<published>2026-11-07T04:10:37Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/feed/packages/commit/?id=52e2e9bd97cecdfe07a71cdaf66a32c60b7f7576'/>
<id>urn:sha1:52e2e9bd97cecdfe07a71cdaf66a32c60b7f7576</id>
<content type='text'>
The debug log printed when detecting the IP address from an interface
did not include the IP family option, while the commands actually
executed use `-4` or `-6` depending on `use_ipv6`.

Include the family option in the log so that it matches the command
that is run.

Signed-off-by: Andy Chiang &lt;AndyChiang_git@outlook.com&gt;
</content>
</entry>
</feed>
