|
My host (xxxx.dyndns.org) has been blocked for abuse, yet I haven't done anything wrong. What's going on? How should I proceed to get my hostname back up and running? |
The question has been closed Sep 05 at 05:27 PM ago by Cry Havok for the following reason "Closing to stop people asking for help here, by posting their question as an "answer".".
|
It is likely because of an abusive update client. Please read this DynDNS Support article for useful information about abuse blocks.
As a side note, upgrading to Dynamic DNS Pro will significantly increase the abuse thresholds, making it harder to get blocked. |
|
If you can't identify all the clients one simply option is to change the password on your account and then configure your chosen update client with the new password. It should be elaborated that it would be possible you having more than one update client running. Only in case you can't identify the update clients, the password change would help. In any other case this is not of use.
Dec 31 at 03:15 PM
RotBlitz ♦
That's the point of my answer ;)
Dec 31 at 08:46 PM
Cry Havok ♦
|
|
Also, some clients can be set to update on a timer, for example ddclient. You should not use that mode as it should only update when your IP has actually changed, however often that is. If it updates when your IP has not changed then that update is considered abusive. Do however leave the timer set to the default (which is likely to be between 25 and 28 days). If you don't then your hostname (and then account) will expire due to lack of activity.
Dec 31 at 03:36 PM
Cry Havok ♦
Free accounts and hostnames expire after a certain period of inactivity, and need to get updated regularly even if the IP never changed. As Cry Havok pointed out, it will be important for users of the free service to leave this interval at a reasonable level. In ddclient, this setting is controlled by the "max-interval" setting, which defaults to 28d (28 days).
Dec 31 at 04:01 PM
VikingTiger ♦
|
