Include No-IP
Brought to you by:
supersandro2000,
wimpunk
Menu
▾
▴
#67 Include No-IP
Hello from No-IP.com
I was reading about the frustration with Dyn no longer offering free accounts. Why not switch the code to No-IP instead? We are free, and have no plans to change that.
Are we even officially included in the client? I see there is a patch for us...
Let us know if there is anything we can do to help.
Dylan
No-IP.com
dzigenis@…
Hi,
Nice to read. I haven't tested the no-ip config yet but it would be nice if there would a link to your API added and if you could verify if all errors are catched by ddclient. Previously I regularly received updates for ddclient written by dyndns people. As I don't have that much time to work on ddclient, it would be nice if no-ip could help on that.
Regards,
wimpunk.
Any news?
How about if the updater works, can anyone write a small addition about it in the wiki?
Thanks,
Shahar
Hello Wimpunk & Shahar...
Thanks for the great replies and the interest.
Here is a link to our API spec...
http://www.no-ip.com/integrate/request/
at the bottom of that page is a link to response/error codes.
You will notice that we have standardized the API and that the only difference between ours and the one you are using for DynDNS is the dynamic dns update server that the updates are going to (dynupdate.no-ip.com vs members.dyndns.org)
Once we get the updater working we can definitely work on adding an addition in the wiki.
My development budget is stretched pretty thin right now, but I've queued up this project and we will have a developer on this in the future (unless you guys beat us to making the change).
Thanks again!
Dylan
Thanks, Dylan.
But, waaaaiiit.... I if this is the same API as dyndns then I would think that a patch isn't actually required, now. Because one would use:
protocol=dyndns2
server=dynupdate.no-ip.com
login=<user name>
password=<password>
ssl=yes
<FQDN of host>
A patch would perhaps make it possible to write 'protocol=no-ip' and leave out the 'server=<...>' option. And perhaps some of no-ip's unique features.
Is this correct, please?
Doesn't quite work. Here's my configuration:
protocol=dyndns2
login=<deleted>
password=<deleted>
use=web
web=dyndns
ssl=yes
<host deleted>
protocol=dyndns2
server=dynupdate.no-ip.com
login=<deleted>
password=<deleted>
ssl=yes
<host deleted>
And here's the output:
shahar@mus:~$ sudo ddclient -verbose
CONNECT: checkip.dyndns.org
CONNECTED: using HTTP
SENDING: GET / HTTP/1.0
SENDING: Host: checkip.dyndns.org
SENDING: User-Agent: ddclient/3.8.0
SENDING: Connection: close
SENDING:
RECEIVE: HTTP/1.1 200 OK
RECEIVE: Content-Type: text/html
RECEIVE: Server: DynDNS-CheckIP/1.0
RECEIVE: Connection: close
RECEIVE: Cache-Control: no-cache
RECEIVE: Pragma: no-cache
RECEIVE: Content-Length: 105
RECEIVE:
RECEIVE: <html><head><title>Current IP Check</title></head><body>Current IP Address: 77.126.208.13</body></html>
SUCCESS: <host deleted>: skipped: IP address was already set to 77.126.208.13.
CONNECT: checkip.dyndns.org
CONNECTED: using HTTP
SENDING: GET / HTTP/1.0
SENDING: Host: checkip.dyndns.org
SENDING: User-Agent: ddclient/3.8.0
SENDING: Connection: close
SENDING:
RECEIVE: HTTP/1.1 200 OK
RECEIVE: Content-Type: text/html
RECEIVE: Server: DynDNS-CheckIP/1.0
RECEIVE: Connection: close
RECEIVE: Cache-Control: no-cache
RECEIVE: Pragma: no-cache
RECEIVE: Content-Length: 105
RECEIVE:
RECEIVE: <html><head><title>Current IP Check</title></head><body>Current IP Address: 77.126.208.13</body></html>
INFO: setting IP address to 77.126.208.13 for <host deleted>
UPDATE: updating <host deleted>
CONNECT: dynupdate.no-ip.com
CONNECTED: using SSL
SENDING: GET /nic/update?system=dyndns&hostname=<host deleted>&myip=77.126.208.13 HTTP/1.0
SENDING: Host: dynupdate.no-ip.com
SENDING: Authorization: Basic <deleted>
SENDING: User-Agent: ddclient/3.8.0
SENDING: Connection: close
SENDING:
syswrite() on closed filehandle GEN2 at /usr/sbin/ddclient line 1816.
Use of uninitialized value $result in numeric ne (!=) at /usr/sbin/ddclient line 1817.
WARNING: cannot send to dynupdate.no-ip.com:443 (Bad file descriptor).
FAILED: updating <host deleted>: Could not connect to dynupdate.no-ip.com.
Dawnlight,
That is correct. The basic API's are very close to each other and above should work just fine...
Not sure why that isn't working, but I'm sure we can figure it out.
Try without SSL
We have another API that some of our clients use which gives advanced features:
Groups
hosts lists
one time authentication ( with the ability to disable clients from our website)
etc;
But for the time being the 'no patch' solution is the way to go.
Do you mind emailing me directly?
dzigenis@…
Dylan
at no-ip.com
Ok, Dylan.
I've sent you a private one.
Let's do this and report back here.
Thanks,
Shahar
Are there any reports to send back here? :-)
It would be great to solve this. I still can't use
SSL.
I've sent you an e-mail, Dylan. Did you get it? Perhaps I've used the wrong e-mail address? It was dzigenis AT no-ip DOT com.
Thanks,
Shahar