D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: jrbilodeau on June 04, 2008, 12:24:20 PM
-
Shortly after upgrading the fw to 1.05 i recieved a message from DynDNS.org for abuse saying that my hardware was sending a update every hour and blocked my hostname. just wondering if this is due to the firmware since i didn`t change anything beside from that
-
I have this setup at home using firmware 1.05 and have not had any issues like this.
-
since i have disabled ddns in the dns-323 and configured it through my linksys router instead it seems to have fix the problem which leads me to believe that its the dns-323. i dont see any other explanation
-
Thank you for your input I will forward this issue you reported to be investigated.
-
Same thing happened to me after upgrading to 1.05.
-
for what its worth i think a bunch of ppl are having this issue check out http://forum.dsmg600.info/t2274-%5BFTP%5D-Dyndns-updater.html
-
I say that DDNS was added to the 323 (don't remember which Firmware release.. I thought 1.0 didn't have it)... I have been doing it through my D-Link WBR-2310 without a problem for about 6ish months now.
-
I would recommend using DDNS from your router. DDNS is not designed to transverse NAT so if you are behind a router doing NAT use the router for DDNS to avoid potential issues.
-
I would just like to chime in that DDNS to dyndns.org was working for me prior to the 1.05 upgrade. Now it is updating every hour, regardless of the timeout value I enter in the config screen.
The point about NAT is well taken, but it was working before the 1.05 update.
Records from dyndns.org:
Jun-25 20:00:07 hostname=mark.is-very-bad.org
myip=70.73.XX.XX
wildcard=OFF
ez-update-3.0.11b7 mipsel-unknown-linux-gnu [] (by Angus Mackay) abuse
Jun-25 19:00:07 hostname=mark.is-very-bad.org
myip=70.73.XX.XX
wildcard=OFF
ez-update-3.0.11b7 mipsel-unknown-linux-gnu [] (by Angus Mackay) abuse
Latest timeout value tried: 56700 (hours)
-
Hmm.. have your reverted back to 1.04 or 1.03 at any point to see if it then works again?