SAOL 1 hour disconnnections?

Hostname Blocked Due To Abuse

Just received a mail from DynDNS stating: "Hostname Blocked Due To Abuse"

I have a 10GB account with SAOL and my account is being reset every 3 hours due to limited GB's left. I understand the problem they face but if wanting to use the DynDNS service supported by many routers you are left with no alternate but to agree to pay for any usage over your CAP :(
 
I have a 4GB unshaped SAOL account and I am unlikely to even use 2GB this month, but because I have now used more than 1GB I am also starting to be hit by this plague. I am glad to hear it can be changed back.
 
AjqNic said:
Just received a mail from DynDNS stating: "Hostname Blocked Due To Abuse"

I have a 10GB account with SAOL and my account is being reset every 3 hours due to limited GB's left. I understand the problem they face but if wanting to use the DynDNS service supported by many routers you are left with no alternate but to agree to pay for any usage over your CAP :(
I think the problem here is your DynDNS client you use. If you disconnect and reconnect, and your IP doesn't change, your client may not send an IP update (this is considered abuse by DynDNS), unless it's been unchanged for more than 2 weeks. If you send DynDNS too many invalid updates, they will kill the relevant hosts. If your router is not playing by the rules, you've got to blame the manufacturer for writing broken (or at least out-of-spec) code.

I only had this issue once, when I was playing with IPCop's "Force Update" button too much. Neither IPCop nor DDClient causes this on DynDNS, regardless of how regularly my connection resets.
 
Valerion said:
I think the problem here is your DynDNS client you use. If you disconnect and reconnect, and your IP doesn't change, your client may not send an IP update (this is considered abuse by DynDNS), unless it's been unchanged for more than 2 weeks. If you send DynDNS too many invalid updates, they will kill the relevant hosts. If your router is not playing by the rules, you've got to blame the manufacturer for writing broken (or at least out-of-spec) code.

I only had this issue once, when I was playing with IPCop's "Force Update" button too much. Neither IPCop nor DDClient causes this on DynDNS, regardless of how regularly my connection resets.
You are correct the problem is the DynDNS client, which in my case is my router (Billion 7202G).

Using a router is far more reliable then running an app on my PC as the router can update DynDNS as soon as a new connection is established, PC clients rely on time based updates and can thus mean the DynDNS address may be incorrect for some of that time between updates. I would assume the "Hostname Blocked Due To Abuse" problem is due to the router updating DynDNS every time a new connection is established rather than when the ip address changes as it is supposed to do.

Unfortunately there is little I can do on my router to correct the problem, maybe a future firmware update will fix this. I don't want to revert back to using a PC DynDNS client as the router option is just so much easier. Prior to the recent 3 hourly disconnects I had successfully been using the router to update DynDNS for a couple of months without hassle so my best option is to go with the paying for the extra usage over my CAP.
 
Last edited:
Daaru said:
I understand that, I'm asking WHY usage is dependant on a session? Something must be maintaining a usage counter during a session else at the end of the session there won't be a counter with the amount of usage during a session.

<rant>It's lameA$$ to claim that the session needs to be disconnected to read this value, actually its not lameA$$ it's retarded, people that write systems like that should never be given a f#ck3n keyboard, rather a broom and an overall and be sent to the streets. Every monkey and his dog can't call themself a programmer just because they can read code, it's the same as claiming that because you can read a bestselling novel that you can write one, can't quite figure out if it was the monkey or the dog that designed this system. </rant>

It's not true though, according to Internet Solutions Telkom / SAIX could quite easily track usage without dissconnection your session. I think it's got something to do with IP address asignment and people moving away from diginet.

It is creating quite a stir.

We've chosen to sell usage based accounts for this very purpose. Users choose thier cap and we bill them for it. If however in the session before the user is capped they pull an extra GB or two they are simply billed for it.
 
ISPA is already taking them to the competition commision, but as I have said in numerous other posts, its a waste of time, all you are doing is feeding a bunch of fat cat lawyers.The CC has already found Telkom guilty, and fined them billions. Telkom says the CC has no authority over them so refuse to pay. Unless you all of a sudden have empowered the CC... why bother with them?
 
Heard on TV news tonight as well that CC has no jurisdiction over municipalities as well (Tswane/Pretoria issue). So CC is toothless?
 
Top
Sign up to the MyBroadband newsletter
X