Posted: Tue Sep 19, 2023 15:32 Post subject: all duckdns down, does not update IP in DDNS
I have had several dd-wrt monitoring different internet lines for more than 5 years. Now I see that all of them have stopped working for me. Some of them have dd-wrt firm from 2022, others from 2016 and others from 2015.
The thing is that all of them have stopped working a few days ago and return this error in the log.
Does anyone have duckdns working with dd-wrt as of today?
My configuration now is:
DDNS Service:Custom
DYNSND Server:duckdns.org
Username:NA
Password:NA
Hostname:xxxxxxx-xxxxx-xxxx-xxxxx-xxxxxxxxxxxxxxx
URL:http://www.duckdns.org/update?domains=casajoselito&token=
Additional DDNS Options:--verbose 5
Do no use External IP Check:Yes
Force Update Interval:1
Joined: 16 Nov 2015 Posts: 6447 Location: UK, London, just across the river..
Posted: Wed Sep 20, 2023 9:00 Post subject:
As you didn't mention you current firmware number...running..ill let you know that, there ware lots of changes and updates on DDNS modules..so update to the last build currently 53469 and research again, lots of threads on the subject...search in the forum or google it ...
I hope someone else will come up with more info to help you out, as im not a DDNS user at all..
Good Luck ! _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
I have upgraded to the latest version of September 2023 and in the DDNS part I see that "duckdns" has been specifically added so I have stopped using the "custom" configuration to try the new one. And everything worked great.
I recommend to all those who have my problem to configure the equipment under the "duckdns" option instead of "custom" and if they do not see the "duckdns" option to update their equipment.
...
