[Ddclient-support] updating too often, now blocked by dyndns
Brought to you by:
supersandro2000,
wimpunk
Menu
▾
▴
[Ddclient-support] updating too often, now blocked by dyndns
|
From: Ian <its...@gm...> - 2007-08-03 17:37:29
|
I got this yesterday. I haven't had trouble like this before, but I'm new to Debian so something has escaped me. root@weasles-ripped-flesh # uname -a Linux weasles-ripped-flesh 2.6.19 #7 SMP PREEMPT Sun Dec 17 22:01:07 CET 2006 i686 GNU/Linux ============ Dear Valued Customer: The hostname, ####.####-####.net, in account ######, has been blocked for abuse. This action has been taken due to the receipt of multiple updates originating from the same IP address. 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 that the host be unblocked at the following URL: https://www.dyndns.com/+dyndns/#####.####-###.net<https://www.dyndns.com/+dyndns/clocker.kicks-ass.net> Please contact su...@dy... if you have questions, queries, or comments regarding this issue. Sincerely, The DynDNS Team ======== When I check #ps aux |less for more than one version of ddclient running, I see only one like this: root 22782 0.0 1.2 9176 6636 ttyp0 S 12:03 0:00 ddclient - sleeping for 280 seconds ======== Here are the contents of my /etc/ddclient.conf. I've changed the refresh from 300 to 600 seconds, but that seems not to have had an effect. I'm restricted to a dial up connecton here. Can someone please point out how my configuration is causing me trouble? root@weasles-ripped-flesh:/var/mail# cat /etc/ddclient.conf <snip> ###################################################################### daemon=600 # check every 300 seconds syslog=yes # log update msgs to syslog mail=root # mail all msgs to root mail-failure=root # mail failed update msgs to root pid=/var/run/ddclient.pid # record PID in file. ssl=yes # use ssl-support. Works with # ssl-library # #use=watchguard-soho, fw=192.168.111.1:80 # via Watchguard's SOHO FW #use=netopia-r910, fw=192.168.111.1:80 # via Netopia R910 FW #use=smc-barricade, fw=192.168.123.254:80 # via SMC's Barricade FW #use=netgear-rt3xx, fw=192.168.0.1:80 # via Netgear's internet FW #use=linksys, fw=192.168.1.1:80 # via Linksys's internet FW #use=maxgate-ugate3x00, fw=192.168.0.1:80 # via MaxGate's UGATE-3x00 FW #use=elsa-lancom-dsl10, fw=10.0.0.254:80 # via ELSA LanCom DSL/10 DSL Router #use=elsa-lancom-dsl10-ch01, fw=10.0.0.254:80 # via ELSA LanCom DSL/10 DSL Router #use=elsa-lancom-dsl10-ch02, fw=10.0.0.254:80 # via ELSA LanCom DSL/10 DSL Router #use=alcatel-stp, fw=10.0.0.138:80 # via Alcatel Speed Touch Pro #use=xsense-aero, fw=192.168.1.1:80 # via Xsense Aero Router #use=allnet-1298, fw=192.168.1.1:80 # via AllNet 1298 DSL Router #use=3com-oc-remote812, fw=192.168.0.254:80 # via 3com OfficeConnect Remote 812 #use=e-tech, fw=192.168.1.1:80 # via E-tech Router #use=cayman-3220h, fw=192.168.0.1:1080 # via Cayman 3220-H DSL Router # #fw-login=admin, fw-password=XXXXXX # FW login and password # ## To obtain an IP address from FW status page (using fw-login, fw-password) #use=fw, fw=192.168.1.254/status.htm, fw-skip='IP Address' # found after IP Address # ## To obtain an IP address from Web status page (using the proxy if defined) #use=web, web=checkip.dyndns.org/, web-skip='IP Address' # found after IP Address # #use=ip, ip=127.0.0.1 # via static IP's #use=if, if=eth0 # via interfaces #use=web # via web use=web # via web # #protocol=dyndns2 # default protocol protocol=dyndns2 # default protocol #proxy=fasthttp.sympatico.ca:80 # default proxy #server=members.dyndns.org # default server server=members.dyndns.org # default server #server=members.dyndns.org:8245 # default server (bypassing proxies) #login=your-login # default login login=###### # default login #password=test # default password password=####### # default password #mx=mx.for.your.host # default MX #backupmx=yes|no # host is primary MX? #wildcard=yes|no # add wildcard CNAME? ## ## dyndns.org dynamic addresses ## ## (supports variables: wildcard,mx,backupmx) ## # server=members.dyndns.org, \ # protocol=dyndns2 \ # your-dynamic-host.dyndns.org server=members.dyndns.org, \ protocol=dyndns2 \ my_virtual_host_name.net ## ## dyndns.org static addresses ## ## (supports variables: wildcard,mx,backupmx) ## # static=yes, \ # server=members.dyndns.org, \ # protocol=dyndns2 \ # your-static-host.dyndns.org ## ## ## dyndns.org custom addresses ## ## (supports variables: wildcard,mx,backupmx) ## # custom=yes, \ # server=members.dyndns.org, \ # protocol=dyndns2 \ # your-domain.top-level,your-other-domain.top-level <snip> <snip> I don't know how to prove the problem is occuring except by the blocking by DynDNS and that isn't satisfactory. Continuing to abuse the privilage of the service for the sake of testing seems lame. Any ideas how I might otherwise do my testing would be appreciated. ======= My mail is still full of messages from ddclient and I've tried restarting it. The mail looks like the following; root@weasles-ripped-flesh:/var/mail# mail Mail version 8.1.2 01/15/2001. Type ? for help. "/var/mail/root": 33 messages 4 new 33 unread U 1 root@Knoppix Thu Aug 2 22:33 23/709 status report from ddclient@weasles-ripped-flesh U 2 root@Knoppix Thu Aug 2 22:43 23/709 status report from ddclient@weasles-ripped-flesh U 3 root@Knoppix Thu Aug 2 22:45 21/492 status report from ddclient@weasles-ripped-flesh U 4 root@Knoppix Thu Aug 2 22:45 21/492 status report from ddclient@weasles-ripped-flesh U 5 root@Knoppix Fri Aug 3 09:23 21/568 status report from ddclient@weasles-ripped-flesh U 6 root@Knoppix Fri Aug 3 09:57 21/624 status report from ddclient@weasles-ripped-flesh U 7 root@Knoppix Fri Aug 3 09:58 23/709 status report from ddclient@weasles-ripped-flesh U 8 root@Knoppix Fri Aug 3 10:03 23/709 status report from ddclient@weasles-ripped-flesh U 9 root@Knoppix Fri Aug 3 10:08 23/709 status report from ddclient@weasles-ripped-flesh U 10 root@Knoppix Fri Aug 3 10:13 23/709 status report from ddclient@weasles-ripped-flesh U 11 root@Knoppix Fri Aug 3 10:18 23/709 status report from ddclient@weasles-ripped-flesh U 12 root@Knoppix Fri Aug 3 10:23 23/709 status report from ddclient@weasles-ripped-flesh U 13 root@Knoppix Fri Aug 3 10:28 23/709 status report from ddclient@weasles-ripped-flesh U 14 root@Knoppix Fri Aug 3 10:33 23/709 status report from ddclient@weasles-ripped-flesh U 15 root@Knoppix Fri Aug 3 10:38 23/709 status report from ddclient@weasles-ripped-flesh U 16 root@Knoppix Fri Aug 3 10:43 23/709 status report from ddclient@weasles-ripped-flesh U 17 root@Knoppix Fri Aug 3 10:48 23/709 status report from ddclient@weasles-ripped-flesh U 18 root@Knoppix Fri Aug 3 10:53 23/709 status report from ddclient@weasles-ripped-flesh U 19 root@Knoppix Fri Aug 3 10:58 23/709 status report from ddclient@weasles-ripped-flesh U 20 root@Knoppix Fri Aug 3 11:03 21/624 status report from ddclient@weasles-ripped-flesh U 21 root@Knoppix Fri Aug 3 11:07 23/709 status report from ddclient@weasles-ripped-flesh U 22 root@Knoppix Fri Aug 3 11:12 23/709 status report from ddclient@weasles-ripped-flesh U 23 root@Knoppix Fri Aug 3 11:27 21/492 status report from ddclient@weasles-ripped-flesh U 24 root@Knoppix Fri Aug 3 11:27 21/492 status report from ddclient@weasles-ripped-flesh U 25 root@Knoppix Fri Aug 3 11:42 21/568 status report from ddclient@weasles-ripped-flesh U 26 root@Knoppix Fri Aug 3 11:43 21/624 status report from ddclient@weasles-ripped-flesh U 27 root@Knoppix Fri Aug 3 11:44 23/710 status report from ddclient@weasles-ripped-flesh U 28 root@Knoppix Fri Aug 3 11:49 23/710 status report from ddclient@weasles-ripped-flesh U 29 root@Knoppix Fri Aug 3 11:54 23/710 status report from ddclient@weasles-ripped-flesh >N 30 root@Knoppix Fri Aug 3 11:59 22/700 status report from ddclient@weasles-ripped-flesh N 31 root@Knoppix Fri Aug 3 12:03 20/482 status report from ddclient@weasles-ripped-flesh N 32 root@Knoppix Fri Aug 3 12:03 20/614 status report from ddclient@weasles-ripped-flesh & 1 Message 1: >From root@Knoppix Thu Aug 2 22:33:16 2007 Date: Thu, 2 Aug 2007 22:33:16 -0400 (EDT) From: root@Knoppix (root) To: root@Knoppix Subject: status report from ddclient@weasles-ripped-flesh WARNING: skipping update of clocker.kicks-ass.net from 205.200.47.254 to 205.200.47.84. WARNING: last updated Thu Aug 2 09:55:54 2007 but last attempt on Thu Aug 2 22:31:54 2007 failed. WARNING: Wait at least 5 minutes between update attempts. regards, ddclient@weasles-ripped-flesh (version 3.7.0) Message 5: >From root@Knoppix Fri Aug 3 09:23:03 2007 Date: Fri, 3 Aug 2007 09:23:03 -0400 (EDT) From: root@Knoppix (root) To: root@Knoppix Subject: status report from ddclient@weasles-ripped-flesh Message 6: >From root@Knoppix Fri Aug 3 09:57:44 2007 Date: Fri, 3 Aug 2007 09:57:44 -0400 (EDT) From: root@Knoppix (root) To: root@Knoppix Subject: status report from ddclient@weasles-ripped-flesh FAILED: updating clocker.kicks-ass.net: abuse: The hostname specified is blocked for abuse; fill in the form at http://support.dyndns.org/abuse.phpto be unblocked regards, ddclient@weasles-ripped-flesh (version 3.7.0) WARNING: cannot connect to checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname 'checkip.dyndns.org Message 32: >From root@Knoppix Fri Aug 3 12:03:48 2007 Date: Fri, 3 Aug 2007 12:03:47 -0400 (EDT) From: root@Knoppix (root) To: root@Knoppix Subject: status report from ddclient@weasles-ripped-flesh FAILED: updating clocker.kicks-ass.net: abuse: The hostname specified is blocked for abuse; fill in the form at http://support.dyndns.org/abuse.phpto be unblocked regards, ddclient@weasles-ripped-flesh (version 3.7.0) ============= Thanks very much for wading through all this. Ian |
