plugout.net

Hi all,

I've created a NO-IP account to make sure I can access the NAS even if its IP changes (which happens now and then).
The account was created successfully and I can access the NAS with the new hostname - which I entered manually.

I activated the DDNS client and entered my NO-IP details. So far so good.
The thing that troubles me a bit is that I see no updates whatsoever, both at the NAS side ('Not Updated, since last restart') and at the NO-IP account page.

I activated

Code: Select all

syslogd

and got a lot of

Code: Select all

user.notice /usr/bin/ez-ipupdate[1659]: try to connect to ip-detection server checkip.dyndns.org:80

messages in my /var/log/messages.

Nothing else though - no connection statement, nothing.

Is this normal?

Thanks,

Rik

Hi rickhabers

Yes it is the expected behaviour. Indeed some month ago no-ip has changed its update request.

So you need the next ddns update daemon which will be included in the next version.

As I am not at home this WE, I am sure fvdw will send you this new file.

Here is the latest version (unpack the zip archive)
You must replace the one currently present in /usr/bin with this one and reboot

If you cannot overwrite the file because it is "busy" then kill the daemon first

Hi fvdw,

I replaced the ez-ipupdate and rebooted. The version for ez-ipdate is now 3.0.11b8, dated 2001.

The messages in /var/log/messages are still the same, however, no-ip does not receive updates.
I dug a bit deeper now and found that the 'wget' method did not work either - no-ip 's site could not be resolved.
The same goes for ping - it gives me a 'bad address'.
Starting to sound like a networking issue.
The NAS is behind a router, with (non-standard) ports forwarded.
The gateway and DNS server addresses point to the router.

I SSH in from a remote location without issues (using the no-ip domain name, btw).

Hints appreciated.

Cheers,

Rik

OK,

Issue solved.
The router does not seem to handle DNS requests well (--> issue that I will need to tackle myself!)
Adding google's DNS to the /etc/hosts solved the issue.

Cheers,

Rik

Hi rikharbers,

As hosts file is overwritten on boot, it is not a good fix.

To solve the dns issue, just set in the fields DNS1 and 2 server of the lan setup menu Ip of openDNS: 208.67.220.220 and 208.67.222.222

Hi Jocko,

Indeed.
Updated the fix, thanks for that!

Of course, after fixing the DNS I hit the next challenge: the NAS is behind the router and started sending the local IP to No-IP ....
I fixed that by disabling the DDNS service in the web-interface and using a shell script that uses wget to get the external IP.
That, combined with the updated ez-ipupdate that only runs if an IP update is detected (compare against the IP known in DNS) I put into a cron job.

This now works :-)

Thansk for the assistance !!

Rik

Ok rikharbers,

But I used the ddns feature since many years to update my no-ip account without any issue. So your issue is amazing :scratch

well,

for now I am happy it works.
The setup is a couple of hundred kilometres from my position - I do everything by SSH (hence the desire for DDNS).
I suspect there is something fishy about the router config - there are two, one used as wireless access point and the other for the rest. Nice opportunities to mix something up. As I do not have SSH access to those, I would need to visit.
Might take a couple of months :-)

Cheers,

Rik