Discuss mailing list

[Jamyn Shanley <jshanley AT gmail.com>]

I have to agree. A blanket statement like "If you're afraid of
traffic, don't host anything public" is just too broad and shifts all
responsibility away from the user, regardless of their actions. As a
general comparison, many mail services throttle, discard, delay, and
filter traffic from heavy sources (You can use Hotmail, Gmail as an
example). Almost all RBL providers will certainly block you if your
queries exceed a threshold per hour/day, if they consider it to be
'too much'.  ISPs filter DDOS attacks, but that doesn't make them
afraid of the traffic, does it? It just means they're taking
responsible action to try to protect their network and the services
they provide.

The responsibility in this case lies with the user. A typical home
user will never generate hundreds of thousands of queries in a short
period. He mentioned the queries were ~ 250,000 in 15 minutes, or
16,600/minute, or 277 queries every second for 15 minutes straight,
from ONE source.

That's excessive. If they really need to generate that many
queries/sec per IP, they should plan ahead and host a LOCAL DNS
server, it's common sense. It's also common sense to protect your
network when it's saturated and becoming unusable.  The end-user
failure to plan for their own needs should not mean that we should
accept the service disruption.

On Tue, Dec 28, 2010 at 11:21 AM,
<discuss-request AT lists.opennicproject.org> wrote:
> Message: 1
> Date: Sat, 25 Dec 2010 18:05:11 -0700
> From: Jeff Taylor <shdwdrgn AT sourpuss.net>
> To: discuss AT lists.opennicproject.org
> Subject: Re: [opennic-discuss] Killed an IP due to excessive usage
> Message-ID: <4D1694C7.5020300 AT sourpuss.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> It's not that I'm afraid of traffic, but this was a sustained stream
> that was pulling a huge amount of bandwidth from a single source.  If it
> was a small burst, I wouldn't have even noticed, but the problem
> continued long enough that I had time to look into it, discover where
> the problem was at, monitor the traffic for a bit, and decide what I
> wanted to do about it.  The traffic had completely stopped ALL other
> internet traffic, so it was disrupting all normal service here.

<snip>

> On 12/25/2010 01:14 PM, G?nter Grodotzki wrote:
<snip>
>> So as I stated already before in the ML, if you are afraid of traffic,
>> don't host anything public. I always welcome any kind of traffic :)
<snip>