LuCI DDNS (v2.8.2-r64) - Individual Service Buttons (Stop/Reload) trigger "XHR request timed out" on OpenWrt 24.10.5

Installing and Using OpenWrt Network and Wireless Configuration
1

Hi everyone,

I'm facing a double issue with DDNS on OpenWrt 24.10.5 (Flint 2 / GL-MT6000). Not only is the LuCI interface bugged, but the IP update itself is consistently failing.

  1. IP Update Failure (The main problem): Despite having a correct configuration for DuckDNS, my IP address is not updating. Even when the service is marked as "Running", the "Last Update" timestamp doesn't refresh or shows an error.

I've tried multiple forcing methods, but the IP remains unchanged.

I suspect a conflict or a timeout issue within the ddns-scripts themselves.

My system logs previously showed "context deadline exceeded" and "Status 500" errors related to services running on my external storage.
IP Update Failure (Log Evidence): My logs consistently show the following error whenever an update is attempted: Tue Jan 13 17:38:24 2026 user.warn ddns-scripts[14942]: peace_wg: Updating IP at DDNS provider failed - starting retry 1/0

The service "peace_wg" is marked as "Running", but it cannot successfully push the IP change to the provider. It seems stuck in a failure/retry loop that never succeeds.

  1. LuCI UI Bug (XHR Timeouts): While trying to fix the update issue, I noticed that the individual Stop and Reload buttons in the Services table do not work.

Clicking them results in a "XHR request timed out" error after a few seconds.

Paradoxically, the global "Stop DDNS" and "Restart DDNS" buttons at the very top of the page do work. It seems the individual service triggers are broken in this LuCI version.

What I have done to fix this:

Hardware Upgrade: Replaced my old USB drive with a brand new 115GB high-speed drive (EXT4) for the /opt partition to ensure no I/O bottlenecks were causing the timeouts.

Fresh Config: Deleted and recreated the DDNS instances.

Permission Check: Verified that all directories (AdGuardHome, ddns logs, etc.) have the correct root:root ownership and 755/700 permissions.

CLI Testing: Running /etc/init.d/ddns restart via SSH works to restart the service, but still fails to push the IP update to DuckDNS.

System Specs:

Device: GL.iNet GL-MT6000 (Flint 2)

OS: OpenWrt 24.10.5

Service: DuckDNS

Is there a known issue with ddns-scripts on the 24.10 branch failing to resolve or push updates? Any help would be greatly appreciated as I rely on this for remote access.
thanks

2

Consider using another DDNS provider instead of Duckdns.

2 Likes
3

like which one would be better ? (free)

4

While there are many good providers around, I can personally recommend dynu.com among others.

1 Like
5

I´m using no-ip.org a few years without problems... but it requires update and check every month.

1 Like
6

Are packages OK?

ubus call system board
opkg list-installed | grep -e ^luci -e ddns
`"`
7

which gets 'boring' (outright annoying) pretty quickly.

8
1 Like
9

I tried many tweaks in the ddns config file, now the last one is that one but still problem is the log

:~# cat /etc/config/ddns

config ddns 'global'
	option ddns_dateformat '%F %R'
	option ddns_loglines '250'
	option ddns_rundir '/var/run/ddns'
	option ddns_logdir '/var/log/ddns'

config service 'DDNS_wg'
	option use_ipv6 '0'
	option enabled '1'
	option lookup_host 'MYNAME.duckdns.org'
	option domain 'MYNAME.duckdns.org'
	option username 'MYNAME'
	option password 'baaxxxxxxxxxxxxxxxxx198d513'
	option ip_source 'interface'
	option interface 'wan'
	option use_syslog '2'
	option ip_interface 'eth1'
	option service_name 'duckdns.org'
	option use_curl '1'
	option dns_server '1.1.1.1'


 18:25:06 EST] user.err: ddns-scripts[29826]: ddns_wg: BIND host error: '1'
[Jan 14, 2026, 18:25:06 EST] user.warn: ddns-scripts[29826]: ddns_wg: Get registered/public IP for 'MYNAMEtrade.duckdns.org' failed - retry 1/0 in 60 seconds