Millions of dynamic DNS users suffer after Microsoft seizes No-IP...
-
The thing is, Microsoft is /was often blamed for these infections. I think they decided they wouldn't be the scapegoat, and had the resources to make one major move a month. No one complains when they take down a spam network. They saw this as the same thing, they just took out a lot of innocents this time. Right or wrong, I bet NO_IP gpt the message. A Guy
-
-
If crimes were being committed, surely US Government agents should be responsible for "taking out" these services (e.g. FBI or similar)?
-
The thing is, Microsoft is /was often blamed for these infections. I think they decided they wouldn't be the scapegoat, and had the resources to make one major move a month. No one complains when they take down a spam network. They saw this as the same thing, they just took out a lot of innocents this time. Right or wrong, I bet NO_IP gpt the message. A Guy
The collateral damage here also wouldn't result in any permanent or serious damage since anything system-critical shouldn't be relying on something like No-IP anyway, and for anything that did this was a great wakeup call to those bad-mannered sysadmins. :P
Overall a beneficial chain of events I think, despite the collateral damage. Sometimes you just can't have your cake and eat it too, no matter which way you cut it.
