Slashdot Mirror


14,000 Domains Dropped Dyn's DNS Service After Mirai Attack (securityledger.com)

chicksdaddy New data suggests that some 14,500 web domains stopped using Dyn's Managed DNS service in the immediate aftermath of an October DDoS attack by the Mirai botnet. That's around 8% of the web domains using Dyn Managed DNS... "The data show that Dyn lost a pretty big chunk of their customer base because they were affected by (Mirai)," said Dan Dahlberg, a research scientist at BitSight Technologies in Cambridge, Massachusetts... BitSight, which provides security rating services for companies, analyzed a set of 178,000 domains that were hosted on Dyn's managed DNS infrastructure before and immediately after the October 21st attacks.
It's possible some of those domains later returned to Dyn -- and the number of actual customers may be smaller than the number of hosted domains. But in the end it may not have mattered much, since Dyn was acquired by Oracle the next month, and TechCrunch speculates that the deal had already been set in motion before the attack.

They also add that "Oracle, of course, is no stranger to breaches itself: in August it was found that hundreds of its own computer systems were breached."

2 of 27 comments (clear)

  1. Re:Good! by frovingslosh · · Score: 5, Informative

    Eloquently stated, but for those that haven't been paying attention perhaps you could have elaborated on your feelings a bit more. My personal dislike for DynDNS is based on their buying up as many of the other free domain services that they could, shutting them down, and then starting to charge for their own previously free service. Fortunately, there are still great free alternatives, such as freedns.afraid.org (which I actually like much better than Dyndns even though my routers don't support it directly).

    --
    I'm an American. I love this country and the freedoms that we used to have.
  2. Re:dubious business pretices by PsychoSlashDot · · Score: 3, Informative

    The problem that I have with Namecheap is that I tried to get a domain from them. Here's what happened:

    I thought of a domain that I would really like to have. I first tried to go to it in my browser and got a 404 error.

    I don't pretend to know everything, but I believe the moment you get a 404 error, that means a web server responded with HTTP response code 404, which requires a} a web server and b} the hostname you typed to have a DNS record resolving to that web server. All of which means: the domain you thought of was already registered before you tried to register it. That you got a 404 the first time and a parking page the second time only suggests the web server is crap.

    Domain squatting sucks, but the sniping activity you're trying to accuse them of doesn't match the symptoms you describe.

    --
    "Oh no... he found the .sig setting."