Print

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

[mrader]

Hello,

I just setup my Dir 825 router.  I am very happy so far.

However, One feature I am trying to use is confusing me.  DDNS setup.

I have an OpenDNS account to setup parental control over the network.  I have a dynamic IP and when it changes I need these updates to be sent to OpenDNS.  I know they have a client that can do this but I want the router to do the updates directly.

When I setup DDNS with Server address "updates.dnsomatic.com"
Host= "all.dnsomatic.com"
and then my login and password it reboots and says staus = disconnect..
Does this mean its not working?
I have also tried to setup OPenDNS by typing the proper address in the server field and this also says disconnect.

I also have a DYnDNS account and when I setup this up it works and reboots and says staus = connect.

Do I need to force an IP change and see what happens or does Staus = disconnect mean it is not working?

[hachi]

I started a topic few threads down for the same problem, with dyndns.com. I don't think this feature is fully/properly implemented yet, or only works with their own dlinkddns.com. I have tried both but neither gives any feedback whether they actually update your ip, it just says "connecting..." --> "disconnect". I know for sure it fails with dyndns, because I lost a domain name to inactivity, with fully configured login/pass.

the "enable" checkbox just does not want to stay set, I don't know if it's supposed to do that or what, but after I update the config it always unchecks itself and grays out the fields again. looks as if it's just there to update the info, but apparently does nothing.

[mrader]

I have not been able to force an IP change yet.  Therefore I do not know if it will update the actual IP address yet.   It does say connected, only when I use a valid hostname as the Hostname.

Example, The Label I use with OpenDNS is "Mynet"  this does not work because it is not a valid dnsname.  If I change my Label on OpenDNS or DNSomatic to "*****@dnsalias.com" it says connected!

"*****@dnsalias.com" is a valid dnsname from DYNDNS and thus works.  It appears to check the validity of the hostname before it says connected or disconnected.

This causes a problem with DNSomatic, they want you to use all.dnsomatic.com as the hostname.  I get disconnected with this since this is not a real DNS name.

Anyone from DLink care to comment on this?  Will we have a new firmware to give us some flexibilty on this?  This feature was one of the reasons I bought this router.  Everyone said it worked on the 655 and the firmware for the 825 had the same ablity to type in other DNS services.

[hachi]

YES thank you, your trial and error has led me in the right direction to get this working.

now obviously the update client is going to be checking for a valid hostname, it is this name that needs to be associated with your pass.

the confusing part, is that they have a dropdown box with 3 choices that *seem* preconfigured with 3 auth domains to be used for each service. those are in fact useless and to be ignored, instead you put the name of *your* domain in that field, to be repeated in the next hostname field below. which makes no sense the way they have labeled the interface, but that's how it works. so the real authentication takes place internally from domain suffix (*.dyndns.org, *.dnsalias.com, etc.) I'm assuming.

to see whether it is working or not, and what the problem is:
- fill in the required info, ignore the input labels and just fill in your own domain twice, then user/pass etc.
- make sure you check "enable" and hit save
- then go to your status tab and check the logs

successful update yields 2 log entries:
(forum is broken, ignore php tags)

Code: [Select]

Successfully updated dynamic DNS entry for my.domain.com good 127.0.0.1

Code: [Select]

Next dynamic DNS update scheduled for d/m/d hh:mm:ss yyyy
failed update yields one of two possible entries:

Code: [Select]

Error updating dynamic DNS entry: DNS Lookup Failed. Will retry later
or

Code: [Select]

Error updating dynamic DNS entry: <badinfo> notfqdn. Please check configuration. Disabling DynDNS

[mrader]

Glad I could help,

I would still like some feedback from Dlink on valid hostnames.

Regards,

[abm100]

I am convinced that this feature is broken in the DIR-825.  I set up my sister's DIR-655 a couple of days ago with dnsomatic with no problems.  It connected to dnsomatic and updated the ip address.  The DIR-825 will not do this.  I have yet to get the DIR-825 to ever update the ip address in dnsomatic.

[sesca]

What are the H/W revisions and F/W version that you guys are having trouble with?

[abm100]

H/W: B1, FW: 2.02NA

[hachi]

I'm on A1/1.10NA here.

it seems to have failed me again, after confirming connection in ui and checking logs to see that it in fact did connect. everything I can see tells me that it's working, and 1 month later I'm still getting expiry problems.

it's possible that the default timeout is too short (576hrs/24days) since dyndns recommends 28 days, even though I never received any abuse warnings. for now I have tried to increase it to 684hrs/28.5days, see if it holds up. I honestly think it has nothing to do with that though, there has got to be some problem with the update protocols that are not showing up in the logs.

very dissapointing since I have a 10 year old linksys and an only slightly newer netgear router that are both capable of carrying out this simple task, with update protocols that are publicly available to anyone.

here are some resources in case your guys are having trouble finding them:

http://www.dyndns.com/developers/specs/flow.pdf
http://www.dyndns.com/developers/specs/syntax.html
http://www.dyndns.com/developers/specs/return.html

[user11]

Was working fine for Rev A1 v1.12NA but is now broken for DynDNS.com using latest v1.13NA. Finally fix DNS-relay, but break DDNS...

[abm100]

I have access to two other models and in my testing, here is what I found with dnsomatic:

DIR-655 A3 1.10 *YES*
DIR-825 B1 2.02NA *NO*
DIR-615 C1 3.11NA *NO*

Who knows, maybe I am doing something wrong, but I did get it to work with one of them.

[hachi]

I have access to two other models and in my testing, here is what I found with dnsomatic:

DIR-655 A3 1.10 *YES*
DIR-825 B1 2.02NA *NO*
DIR-615 C1 3.11NA *NO*

Who knows, maybe I am doing something wrong, but I did get it to work with one of them.

are you saying those 2 don't connect at all, or not doing the monthly refresh? better to be specific, if they plan to figure this out. for the former, try the method in my post above. in my case it seems to make the first connection, but just lets the domain expire at the end of the month, I've had to re-register twice in the last 2 months.

[sesca]

I'll try these routers/firmwares myself and see if I can make the initial connections. If I get the same results as you guys, I can report it. If it works, we'll go from there.

[abm100]

Hi Hachi,

I have been corresponding with sesca in the private messages area with details, sorry about not having specifics here.  On the DIR-655, when I hit 'Save', the screen stays there and shows a connection being made.  On DNS-O-Matic, the update occurs.  On the DIR-825 and the DIR-615, after I hit 'Save' the screen changes to one that says wait for 15 seconds and after that a 'Continue' button appears after the time counts down to zero.  The Status says 'Connected', but no update to DNS-O-Matic ever occurs.

[jetspeedz]

Has this been resolved with the latest 2.03 Firmware? with updates for dyndns?