Posted: Fri Dec 01, 2023 19:40 Post subject: DDNS issue v3.0-r54109 std (11/24/23) R8000
Hi,
I updated to this Firmware: DD-WRT v3.0-r54109 std (11/24/23) last week and have been having DDNS issues since.
My configuration has not changed, yet I get this error:
Update forced for alias ef595166-xyxy-4e3c-xyxyxy-zyzyzyzyzyz, new IP# 192.168.0.99
Fatal error in DDNS server response: DDNS server response not OK
Error response from DDNS server, ignoring ...
Joined: 16 Jun 2006 Posts: 152 Location: Germany, BW
Posted: Fri Dec 01, 2023 21:40 Post subject:
your alias looks like the Username, the alias is your dns name (in the GUI the Hostname), something like myname.hopto.org.
The new IP is also wrong, its a private IP, but must be your Internet IP. Did you activate "Use Externam IP Check" and "Use SSL"? Try only one of these settings and then both together until you get the external IP.
Thanks, so I got the external IP by putting both the ticks.
However I tried putting my username in Hostname in the GUI, but still get an error.
SO, do we not need to put Hostname Hex as per the DDNS server indications?
Update forced for alias xxxxxxxxx, new IP# xxx.xx.9.xx
Fatal error in DDNS server response: DDNS server response not OK
Error response from DDNS server, ignoring ...
My DDNS server is DuckDNS. I am not sure if it is the recommended one but it's free and have been using it for 2 years+ without any issues.
The configuration they recommended is like this:
DDNS Service:Custom
DYNSND Server:duckdns.org
Username:NA
Password:NA
Hostname:af345123-6e27-4e3c-94ad-379239da1c54
URL:http://www.duckdns.org/update?domains=myname&token=
Additional DDNS Options:--verbose 5
Do no use External IP Check:Yes
Force Update Interval:10
I have changed it a bit to remove private info.
Thanks
Thanks for the info.
I actually just realized Duck DNS was added to the list.
I have tried inputting the information as provided by DuckDNS page, such as hostname which is that long hex data, but what do I put as Token?
Also, I cannot seem to access SSH. In Admin/Management SSH management is disabled and greyed out.
Joined: 18 Mar 2014 Posts: 12922 Location: Netherlands
Posted: Sat Dec 02, 2023 13:25 Post subject:
bobby121418 wrote:
Thanks for the info.
I actually just realized Duck DNS was added to the list.
I have tried inputting the information as provided by DuckDNS page, such as hostname which is that long hex data, but what do I put as Token?
Also, I cannot seem to access SSH. In Admin/Management SSH management is disabled and greyed out.
Thank you.
I can now access SSH, but my password does not work. I used my router admin username and password, but cannot get in. Am I using a wrong user/password?
Also, please tell me what I should put for the DDNS Token?
Thanks
Joined: 18 Mar 2014 Posts: 12922 Location: Netherlands
Posted: Sat Dec 02, 2023 15:16 Post subject:
From the wiki:
Quote:
When asked for the username, enter root (even if you changed username in web interface)
When asked for the password, enter your router's password (default "admin")
Also, please tell me what I should put for the DDNS Token?
Thanks
See my answer above
ho1Aetoo wrote:
The strange HEX number is logically your token and the hostname is your dyndns URL
By the way, it also says on the duckdns page that this long number is your token and not the hostname so I don't know what kind of nonsense you are doing.
and your hostname is i-am-blind-and-cannot-read.duckdns.org
Just to be clear, as per DuckDNS own helpful information (see image) it suggests the long HEX as the Hostname.
However, following your note, I put the long HEX as the Token.
I have tried various things for the Hostname, such as
duckdns.org
I get the following error:
In-a-dyn version 2.12.0-dev -- Dynamic DNS update client.
Update forced for alias duckdns.org, new IP# 91.xxx.yyy.zzz
Fatal error in DDNS server response: DDNS server response not OK
Error response from DDNS server, ignoring ...
In-a-dyn version 2.12.0-dev -- Dynamic DNS update client.
Failed resolving hostname mydomain: Name does not resolve
Update forced for alias mydomain, new IP# 91.xxx.yyy.zzz
Updating IPv4 cache for mydomain