-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello,
Just thought I should post my thoughts on this as well as clarify the way DynDNS implements bans on hostnames for abusive updates. First, our host blocks are not triggered by a short update interval itself. Abuse blocks are triggered when a threshold is met of a number of unnecessary updates being sent between good updates. This means if your update client is configured to send us updates every 5 minutes regardless of whether your IP address has changed, it will trigger an abuse block unless your IP address changes very often. Setting the interval between checks to 5 minutes is a non-issue so long as ddclient is configured to run as a daemon and only send updates as necessary. The proposed patch in bug 513626 will generate this configuration out of the box with debconf for users that select DynDNS as their service. In my opinion the best fix for this is not adding warnings to ddclient or preventing certain configurations entirely, but rather generating a good default configuration for users based on their debconf answers. Regards, - -- Dan McCombs Dynamic Network Services, Inc. http://www.dyndns.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmn6GEACgkQSTakzmXY5/hQaACdHoLnDJK1kEDIeBUM5yAwxJRd 2K8An1zxm2v+4uxesI8ij4IZDp/FXcFP =xkQk -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
