Duckdns on Asus merlin router

[Aidancov1]

I am trying to get duckdns to work on my Asus router. I have followed a few tutorials but the seem to be outdated and don't work. It says on Asus merlin website that you need to run a script for custom ddns in Jffs/sripts which I have tried to do but it either says DDNS in processing or error.

Can anyone assist with this please.

Thank you.

 

[commodoro]

Hi,

I also use duckdns for the DDNS and I have made a inadyn.conf file under /jffs/configs with the following content:

provider duckdns.org {
        hostname = xxxxx.duckdns.org
        password = noused
        username = xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx
        checkip-command = 'getrealip.sh'
}
period = 60
forced-update = 60
iterations = 0
iface = eth4
ca-trust-file = /etc/ssl/certs/ca-certificates.crt
secure-ssl = true

where username is the token that you can find on the duckdns home

and on DDNS from web GUI of router i have made the following conf

I hope that information would help you

Edit

Sorry I have missed this part, added under /jffs/scripts/ a script called ddns-start and inserted the following:

#!/bin/sh

inadyn --once -f "/jffs/configs/inadyn.conf" -e "/sbin/ddns_custom_updated 1" --continue-on-error "/sbin/ddns_custom_updated 0"

 

[Chuckles67]

Same as OP: I'm testing a DuckDNS custom DDNS setup.

A useful test command when SSH'd into the router is this.

inadyn -l debug -n --once -f "/jffs/configs/inadyn.conf"

This command taken from the Merlin Wiki webpage. Look in the console for this reply from DuckDNS.org "Server response: HTTP/1.0 200 OK". The OK (not KO) indicates success.

 

[Chuckles67]

The Wiki states the folder location should be this.

/jffs/inadyn.conf

In my testing the suggestion here to use the sub-folder "configs" seems to work.

/jffs/configs/inadyn.conf

 

[PaddraighOS]

Good tips from both above. A few extra things worth checking if you are still seeing DDNS in processing or errors:
1. Make sure DDNS Provider in the router GUI is set to Custom - if you leave it on DuckDNS (the built-in option), it runs its own update client which conflicts with inadyn. Setting it to Custom hands control to inadyn instead.
2. The iface line in the config (eth4 in commodoro's example) is the WAN interface and this varies by router model. SSH in and run nvram get wan0_ifname to confirm yours. On some models it is eth0, eth4, or ppp0 for PPPoE connections. Wrong iface means inadyn watches the wrong interface for IP changes.
3. After editing inadyn.conf, restart inadyn cleanly with service restart_inadyn from SSH rather than rebooting - much quicker to iterate on.
4. The debug command Chuckles67 posted is the best diagnostic tool. The OK versus KO in the server response tells you immediately whether DuckDNS accepted the update. If you get OK there but the router GUI still shows processing, the issue is in the DDNS provider setting in the GUI rather than inadyn itself.

 

[Chuckles67]

Hi,

I also use duckdns for the DDNS and I have made a inadyn.conf file under /jffs/configs with the following content:

provider duckdns.org {
        hostname = xxxxx.duckdns.org
        password = noused
        username = xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx
        checkip-command = 'getrealip.sh'
}
period = 60
forced-update = 60
iterations = 0
iface = eth4
ca-trust-file = /etc/ssl/certs/ca-certificates.crt
secure-ssl = true

where username is the token that you can find on the duckdns home

View attachment 62309

and on DDNS from web GUI of router i have made the following conf

View attachment 62310

I hope that information would help you

Edit

Sorry I have missed this part, added under /jffs/scripts/ a script called ddns-start and inserted the following:

#!/bin/sh

inadyn --once -f "/jffs/configs/inadyn.conf" -e "/sbin/ddns_custom_updated 1" --continue-on-error "/sbin/ddns_custom_updated 0"

The GUI offers forced update intervals in days, not seconds. This seems too frequent:

forced-update = 60

See this thread comment on the same topic.

The period also seems frequent.

period = 60

DuckDNS.org install example for Linux suggests 5 minutes. This duckdns.conf example on Merlin repo sets period at 30 minutes.

Why so frequent? Did you find issues with less frequent updates?