Edit:
apologies for the vagueness of my "unusable" statement please let me clarify below...
Guspaz wrote:
There's a difference between "don't want to use because the packets don't sit right with me" and "the linode is unusable". Let's be clear, the linode is perfectly usable (for anything but DNS serving). If I said "I don't want to use my linode because it's a full moon and also a Tuesday", that doesn't somehow make my linode unusable (unless it's a werelinode, but that's another issue). It just means that I haven't restocked on silver USB keys recently.
What I said was
asp wrote:
I guess I'm (incorrectly?) hung up on the fact that regardless what the numbers are legitimate traffic would be competing with this DNS noise and that just doesn't sit right with me.
In other words legitimate traffic would be competing with the traffic from the attack and that's what didn't sit right with me. Does the linode work? Well yes I said that in my inital post, but I followed that I'm not going to use a machine for business purposes while it's under attack thereby making it unusable to me.
I really don't think the previous statement is unreasonable. I apologize if I made it sound like linode's service is not totally awesome because it is. I've been a very happy linode customer for years, but this has never happened to me before which is why I was asking the community for help/perspective.
So you would have just ignored the attack, or noticed it an just said "whatever..." based on your statements below?
Guspaz wrote:
Basically, you don't pay for inbound traffic, so if you just drop the inbound DNS traffic, there is no impact on your linode. You've got four cores to play with (so effectively 400%), so 15% usage isn't a problem unless you're maxing out all four cores. The only scenario where you might see some impact is if you're trying to run a DNS server, but there's not really any reason why you would since Linode provides free DNS servers both for resolution and hosting.
BTW it's freaking awesome that we don't have to pay for inbound traffic. I really would have been screwed otherwise. I was also saved by the fact that I was alerted when the inbound connections got to a certain rate...
Thanks again for the help!