Posted: Wed May 23, 2018 11:34 Post subject: DD-WRT version of inadyn does not work with INWX
Dear experts,
I tried to solve the following topic for quite some time, read a lot of articles/pages and spent some nights in the meanwhile but unfortunately without any progress:
This is what I need:
INWX DDNS update url needs to look like: "https://dyndns.inwx.com/nic/update?myip=ww.xx.yy.zz" where ww.xx.yy.zz is the router's WAN ip (which changes almost daily). It works perfectly if you do it via any browser.
Problem:
As per logging inadyn always appends the hostname to the url. I haven't found a way to disable this or make inadyn to do it right. Also options like "append-myip=true" or using a variable "%i" in the update-url like it is documented for newer versions does not work. And it always says "Update successful" but actually it isn't...
Does anybody have a hint for me how to...?
Many Thanks,
Chris
Config: Asus AC-68U / Kong build from 19/02/18 / inadyn configuration via GUI
The hostname comes from the field hostname in the GUI (I also should have canceled this, but posted too fast).
You are right this seems to be exactly the problem. I did not find a way to tell the inadyn that is should append the IP instead of the hostname. I suspect, that there is some special functionality when you specify something in "<..>" because it does not show up in the "GET ..." log-line. But I did not manage to find the correct "variable name" ...
I had the same issue an dtalked to INWX support. They told me that the ADV (1.96-ADV) is not the latest one. It should work with version 2.00.
By now I lost a week of internet by bricking my router in the process of doing an update... I just brought it back to life with the latest available firmware and ADV is still version 1.96.. so this will be no solution
Unfortunatelly I couldn't make real progress so far in my case. INWX TechSupport has a setting on their server, that the DDNS service ignores whatever parameter is passed on to the service. But in my case this doesn't work because the DDNS update goes out on VPN and I need the "not-VPNed" IP there. This is actually not my highest priority. I'll keep the topic updated.
@development team: The easiest way to overcome all that would be the update of this package to the lastest version available version in one of the next builds...