freedns.afraid.org not working

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1.Enter hostname (blahblah.us.to)
2.Enter email and enter ddns key (Mine is a random string of letters & numbers. 
I removed the question mark (tried with and without)
3.Click apply then update

What is the expected output? What do you see instead?
Expected output is url query is sent to freedns successfully and subdomain's 
forwarding address is updated. What actually happens is the URL Query fails.

What version of the product are you using? On what operating system?
Using the RT-N65U 3.0.3.8-081, on Windows 7 x64 Ultimate.

Please describe the problem as detailed as it's possible.
If you have connection problem, then syslog file is required. (please do
attach it as a file)
Note that if there will be a poor problem description the issue status will
be changed to 'Invalid'!

Log says:

Inadyn version 1.99.2 -- Dynamic DNS update client.
Resolving hostname eatinginternet.us.to => IP# 174.24.xxx.xx
Checking for IP# change, connecting to checkip.dyndns.org(216.146.43.70)
Update needed for alias eatinginternet.us.to, new IP# 75.172.xx.xx
Sending IP# update to DDNS server, connecting to 
freedns.afraid.org(204.140.20.21)
Sending update URL query, connecting to freedns.afraid.org(204.140.20.21)
Update URL query failed

Original issue reported on code.google.com by ikramare...@gmail.com on 7 Jan 2015 at 6:38

GoogleCodeExporter commented 8 years ago

I will update to the nightly 3.0.3.9-090 tomorrow (hopefully) and see if that 
resolves the problem.

Original comment by ikramare...@gmail.com on 7 Jan 2015 at 6:40

GoogleCodeExporter commented 8 years ago

Issue still present, now using 3.0.3.9-090 for RT-N65U. Hostname is entered, 
then the token in the token field. Apply then update. Log says

inadyn[628]: FORCED_UPDATE command received, updating now.
inadyn[628]: Checking for IP# change, connecting to checkip.dyndns.org 
(91.198.22.70:80)
inadyn[628]: Querying DDNS checkip server for my public IP#: GET / HTTP/1.0^M 
Host: checkip.dyndns.org^M User-Agent: inadyn/1.99.12 troglobit@gmail.com^M ^M
inadyn[628]: Checked my IP, return code: 0
inadyn[628]: IP server response:
inadyn[628]: HTTP/1.1 200 OK^M Content-Type: text/html^M Server: 
DynDNS-CheckIP/1.0^M Connection: close^M Cache-Control: no-cache^M Pragma: 
no-cache^M Content-Length: 103^M ^M <html><head><title>Current IP 
Check</title></head><body>Current IP Address: 75.165.x.xx</body></html>^M
inadyn[628]: No IP# change detected, still at 75.165.8.70
inadyn[628]: Update forced for alias eatinginternet.us.to, new IP# 75.165.x.xx
inadyn[628]: Sending IP# update to DDNS server, connecting to 
freedns.afraid.org (204.140.20.21:443)
inadyn[628]: Sending IP# update to DDNS server, initiating HTTPS ...
inadyn[628]: SSL connection using DHE-RSA-AES256-SHA
inadyn[628]: SSL server cert subject: /OU=Domain Control 
Validated/OU=EssentialSSL/CN=freedns.afraid.org
inadyn[628]: SSL server cert issuer: /C=GB/ST=Greater 
Manchester/L=Salford/O=COMODO CA Limited/CN=EssentialSSL CA
inadyn[628]: Sending update URL query, connecting to freedns.afraid.org 
(204.140.20.21:443)
inadyn[628]: Sending update URL query, initiating HTTPS ...
inadyn[628]: SSL connection using DHE-RSA-AES256-SHA
inadyn[628]: SSL server cert subject: /OU=Domain Control 
Validated/OU=EssentialSSL/CN=freedns.afraid.org
inadyn[628]: SSL server cert issuer: /C=GB/ST=Greater 
Manchester/L=Salford/O=COMODO CA Limited/CN=EssentialSSL CA
inadyn[628]: Successfully sent DDNS update using HTTPS!
inadyn[628]: Successfully received DDNS update response (184 bytes) using HTTPS!
inadyn[628]: Update URL query failed
inadyn[628]: Sending alias table update to DDNS server: 
inadyn[628]: SSL_write FAILED! (err: 5)
inadyn[628]: DDNS server response:

Original comment by ikramare...@gmail.com on 7 Jan 2015 at 8:49

GoogleCodeExporter commented 8 years ago

Also, there is a bug in the code. So freedns uses a token system where it has a 
predefined address to go to, and at the end a user's token is added. The token 
corresponds to a specific subdomain that is registered in the system. The 
freedns server then automatically updates the ip of that subdomain based on the 
ip of the client that issued the request to the server with the token. So 
really, for the freedns ddns service, it should just go to 
"http://freedns.afraid.org/dynamic/update.php?[TOKEN]" which would make the 
whole process a whole lot simpler. I don't know why this wasn't done in the 
first place, because code can be written to easier determine whether or not the 
ddns update was successful as the freedns page mentioned is just plain text and 
even mentions whether the update was successful or not. Seriously, shouldn't be 
this complicated.

Original comment by ikramare...@gmail.com on 7 Jan 2015 at 8:54

GoogleCodeExporter commented 8 years ago

Oh by the way, the bug I meant was that the hostname field is required for 
freedns, but freedns couldn't give a shit about hostname: all it cares about is 
the token.

Original comment by ikramare...@gmail.com on 7 Jan 2015 at 8:56

GoogleCodeExporter commented 8 years ago

You know, this issue should be addressed to the Inadyn project, I think.

Original comment by d...@soulblader.com on 9 Jan 2015 at 9:20

javitu / rt-n56u

freedns.afraid.org not working #1394