Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[madpenguin]

Hey. Apparently every time you reboot the 323 it calls for an update. Didn't know this until I recieved an email from DynDNS.org stating that my account was banned for abuse.

I just swapped out the drives for larger ones and wound up rebooting the thing several times. This would be nice if this issue was taken care of in a firmware update...

Just an FYI for everyone here.

[Shadymedia]

They banned me as well but for a different issue

Is was just trying to update by it's self

I disabled the function

Thankfully I have a static IP address so i just enter it in manually and my issue was 

[madpenguin]

O.k... Your right. It is updating all by itself because I just got banned again after getting reinstated.

This all started to happen after the 1.05 firmware update. I've had no problems for the past year until now. Time out is set at 24 hours....

Grrrrrr...... Looks like I'll have to try and backwards flash to 1.04. That or investigate the use of a software client.

Did this also happen on 1.05 firmware for you? Thanks for the reply BTW...

[madpenguin]

I don't suppose a mod here could make a quick statement about this problem could they?

I assume these are the "official" dns-323 forums? I noticed 1.06 isn't going to fix this.

Is this being looked into? Is dlink even aware that 1.05 broke the dyndns updating (1.04 worked for a year without issues)?

Thanks for any official response on this matter. I would certainly appreciate it....

Trying to fix it myself but no joy so far:
http://forum.dsmg600.info/t2274-%5BFTP%5D-Dyndns-updater.html

[ttmcmurry]

There is another recent thread on this subject:

http://forums.dlink.com/index.php?topic=2752.0

The short of it:  try this from a router first.  If it doesn't work on your router, do it on the 323 as a last resort.  The 323 can't detect changes in the WAN like your router does.  The 323 has to keep trying by asking or just sending blind updates.

[madpenguin]

Thanks for the link. Looks like I'll have to fix it myself with funplug.

None of the obstacles or limitations expressed here or on the other 323 forum are valid. Set cron to run every 15 minutes using whatismyip. That would take care of an instance when your IP actually changed and wouldn't query the dyndns server unless it actually changed.

How to go about keeping your account from expiring is a little more tricky but offhand I could set a cronjob to run every 25th day to force an update regardless of whether or not your IP has changed. That wouldn't work if you lost power tho. The 25 day cycle would be reset (I think).... I'll figure something out, I'm sure.

This isn't rocket science so I'm assuming the lack of action from dlink is just incompetence rather than a lack of desire to address the issue. I could excuse "incompetence" but to blatantly leave it broken like this for so long out of sheer uninterest for their paying customers is inexcusable IMO...

BTW, my router doesn't have this functionality and I'm opposed to using a software client on my PC. This is THE main reason I bought the 323. It had an FTP server and dyndns updating capability.... Anything other than a fix 323 side isn't acceptable to me.

[ECF]

Try the new firmware 1.06 this should no longer be an issue.

[mamurao]

I have been banned as well before from dyndns.org when i configured DDNS on DNS-323 under 1.05. I made a workaround, instead i configured DDNS on the router and port forward to the DNS-323 . All good since then.