Network Solutions Customer Site Compromises and DDoS

July 17, 2013 - 20 Comments

Network Solutions is a domain name registrar that manages over 6.6 million domains. As of July 16, 2013, the Network Solutions website is under a Distributed Denial of Service (DDoS) attack. Recently, Network Solutions has been a target for attackers; in a previous outage, domain name servers were redirected away from their proper IP addresses. This was reported to be a result of a server misconfiguration while Network Solutions was attempting to mitigate a DDoS attack. It is possible that the DDoS attacks are related.

According to, the Network Solutions site has been having issues for at least the last 24 hours.


Response time in ms (GMT -8:00)

Initially, Network Solutions reported that:


Posted July 16, 2013

However, in the comments it was made clear that Network Solutions decided to temporarily remove this thread from their Facebook page so that customers affected by the DDoS could more easily find relevant information. There were multiple reports on the July 16, 2013 Facebook thread that appear to indicate customer DNS records were corrupted before the DDoS induced outage. As a result of the DDoS attack, any customers that were compromised previously may not be able to repair their domain name infrastructure until the DDoS is mitigated.


The Cisco TRAC team is continuing to monitor the situation for further developments.

Special thanks to Jaeson Schultz for his help with this post.

In an effort to keep conversations fresh, Cisco Blogs closes comments after 60 days. Please visit the Cisco Blogs hub page for the latest content.


  1. So what recourse do we have? This is killing us today. NetSol has absolved themselves of all responsibility and instructed us to call

  2. You can view the current and past response times for the main site here –

  3. Was this resolved? Such a big company has a big problem when it goes about DDOS

  4. How did everyone survive the aftermath? After my site was back up, I didn’t see any major problems from about 11am cst onwards.

  5. have a few sites with them..hope the issue is resolved before the weekend..

  6. I had a large customer that had several complaints of DNS issues around 4:30p.m. to 6:30pm central. There domain is registered via NS…do you have any more information on this?

  7. Hi
    this network issue just put a big trouble

  8. Things seem to have smoothed out. Any updates if this is a temporary reprieve or if the problems are resolved?

  9. We are seeing instances where the root servers are pointing to NSI Name Servers instead of ours. They seem to be assuming that they host DNS for the domains but seem to be proxying the results from our name servers to the outside world because the are still resolving. By following the trail in it’s going to I.ROOT-SERVERS.NET. [](117ms) > [](50ms) > [](46ms)
    where the last hop for the domain should be our own name servers, not

  10. We are affected by this off and on this morning, and as of right now we are still having DNS issues. thank you cisco blogging for the coverage as NS has not given any update and their phones are dropping off the hook now.

  11. If your site’s DNS servers are down, there is an easy workaround (assuming you know the IP addresses and host names of your web, e-mail, etc. servers and you have login info for your domain registrar). Sign up for another DNS host, add your DNS records, and configure your domain name with your registrar to use the new DNS servers. Ideally, you should host your DNS records with multiple providers to begin with, which would have prevented problems like this from occurring.

    • So one of the problems we are having is that Network Solutions IS the registrar. So this isn’t possible. ;(

    • I’m pretty sure you can’t use Network Solution’s own DNS servers for a domain/zone unless they’re also your registrar. So what if you’re unable to login to your registrar to change the name servers? Or let’s say you can change them, or they already do point to different providers for primary and secondary DNS, this wouldn’t do any good if the registrar itself is either not giving that information out to begin with, or worse giving the wrong servers because they’ve been hijacked. Name server pointer changes at the registrar also take the longest to propagate in my experience, at least 24 hours. It’s not something you do in response to a problem.

  12. Do we know if it’s been resolved?

    • It seems to have been at around 11ish EST. But many of my domains dns servers are not resolving again. Started about 3:30p EST

  13. Wonder if their stock will go down too :~

  14. Finally someone with some answers. Apparently Network Solutions doesn’t understand that we (IT PRofessionals) need to keep our customers up to date. Without any information you make us look like idiots when in fact its Network Solutions with their head up their a….

  15. Ahh…real facts. This is actually the best summary of all the info on the attack I’ve found.