dyndns domain blocked... too frequent updates

Posts: 3 · New Forum Member Joined: Jan 07, 2006 Posts: 3

My equipment WRTP54G. Below is the message received from dyndns.org regarding the frequent updates. I use the router's built in updating for dyndns if that wasn't obvious from the subject. Is this a known issue? My Current firmware version is 1.00.58.

Dear Valued Customer:

The hostname, somename.dyndns.org, in account someaccount, has
been blocked for abuse. This action has been taken due to the
receipt of multiple updates originating from the same IP
address.

Please note, updates which result in the IP address associated
with a host changing are NOT considered abusive. Only those
updates which result in no change to the host are abusive.
Please take a moment to review our Update Abuse Policy here:

http://www.dyndns.com/support/abuse.html

It is vital that you correct the problem which is resulting in
these repeated and unnecessary updates. Once you have corrected
this problem, you may request the host be unblocked at the
following URL:

https://www.dyndns.com/+dyndns/somename.dyndns.org

If you are using a hardware router's built-in update
functionality, it is most likely not properly functional; we
recommend that you contact your router's manufacturer regarding
this issue and ask them to contact us for assistance correcting
their products to interface properly with our systems.

Please contact support@dyndns.com if you have questions,
queries, or comments regarding this issue.

Sincerely,
The DynDNS Team

Posts: 60 · Posted: Sat Jan 07, 2006 12:34 am Post subject:

I tried using my other routers DNS updating before and it would never update. I think it can only send the info once a month without being abuse - if I remember correctly. They had a program for updating the addresses on the website I used and it worked great.

http://www.dyndns.com/support/clients/

Posts: 3 · New Forum Member Joined: Jan 07, 2006 Posts: 3

Yes I realize that there are other updating clients. The policy is only to update if the IP address changes. If I can avoid using other clients I would like to do so. Considering this is a feature that comes with the router specifically for dyndns I would assume that if the feature causes conflicts that it may need to be resolved (in a picture perfect world).

Posts: 605 · Posted: Sat Jan 07, 2006 11:03 am Post subject:

Im lucky if my RT31P2 does the dyndns updates Rolling Eyes

It says it updates but it really doesnt.

Posts: 476 · Posted: Sat Jan 07, 2006 11:36 am Post subject:

I broke down and started using DynDNS Updater a long time ago and it has worked very well for me so far.

Posts: 182 · Posted: Sat Jan 07, 2006 1:36 pm Post subject:

You could also get your ISP to provide you with a static IP address, or change to one that does.

Posts: 192 · Posted: Sat Jan 07, 2006 11:18 pm Post subject:

I also noticed the WRTP54G doing unnecessary DynDNS updates so I turned it off. It turns out that this hardware is NOT certified by DynDNS. See the following link for a list of certified hardware clients:

http://www.dyndns.com/support/clients/hardware/

Don't confuse the WRT54G, which IS certified, with the WRTP54G.

Also, DynDNS doesn't recommend ANY hardware client, even if it is certified (strange but true). See this link also.

http://www.dyndns.com/support/kb/archives/why_we_recommend_software_clients.html

I sympathize. I'd also like to use the built-in router feature, but it just doesn't seem reliable.

Posts: 3 · New Forum Member Joined: Jan 07, 2006 Posts: 3

Yes I noticed that it wasn't on the certified list. Without looking into anything in detail I would assume that they share some of their gpl codebase. I can't imagine that they rewrite the code for every product. So the lack of certification doesn't entirely scare me away.

I have used it for a while in the past and it worked fine. So I got the account unblocked and I'm blaming it on a fluke, hoping for the best. This is more of an experiment than anything. It is nice to keep a collection of my school projects available for myself at home. So if this fails I may later decide to fork over the extra cash for a static ip, but until then I'll keep my fingers crossed.

I'll post again in a few days to update success or lack thereof...

Thanks for the replies.