Print

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

[heartsofwar]

Code: [Select]

Current Firmware Version: 1.12, Thu 22 Sep 2016
Current Firmware Date: 2016-09-22 17:57:00

DDNS settings
----------
Server Address: dynupdate.noip.com  |  Manual
Host Name: ########
Username: ########
Password: ########
Time Out: 1 hours


• DDNS tries to update the server every minute despite the timeout being set to 1 hour when using a server address in the form of a hostname

Code: [Select]

[Time]Thu Jan 12 14:08:18 2017
[Message:1]Update '#########' to 'no-ip.com' successfully, the IP address ((NULL)) is not changed.
--------------------------------------------------------------------------------------------
[Time]Thu Jan 12 14:09:19 2017
[Message:2]Update '#########' to 'no-ip.com' successfully, the IP address ((NULL)) is not changed.


NoIP reports: The last update - 1 minute ago

• DDNS won't work if the server address is in the form of an IP address instead of hostname
NoIP reports: The last update - 6 days ago

• Logging doesn't show the IP address, it shows NULL, and the server isn't actually updated

[FurryNutz]

I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. Please reference this forum thread as well. We find that phone contact has better immediate results over using email.
Let us know how it goes please.

[FurryNutz]

Might check the new v1.13 FW update and see. I don't see any information regarding fixes or new features and not sure what ERP is. 

[heartsofwar]

I updated to 1.13, but I see the same results. I have sent an e-mail, but I may call if it becomes more pressing. Thanks

[FurryNutz]

Ok, keep us posted if you get any response. I presume this is just a bug in the handling of DDNS services.

Internet Service Provider and Modem Configurations

• What ISP Service do you have? Cable or DSL?
• What ISP Modem Mfr. and model # do you have?

[FurryNutz]

Any status on this? 

I updated to 1.13, but I see the same results. I have sent an e-mail, but I may call if it becomes more pressing. Thanks

[heartsofwar]

I am running a modified 1.13B03 firmware which seems to fix the issues I was having. When support team will push it out public is unknown.

[FurryNutz]

Glad they resolved your issue. Enjoy. 

[FurryNutz]

Looks like it was posted here:
v1.13B03 Beta