Cisco Logo


Security

UPDATE: This blog post is related to the redirection of domain name servers that occurred back in June 2013.  This post is NOT related to the ongoing activity occuring July 16, 2013.  Cisco TRAC is currently analyzing the ongoing issues with Network Solutions’ hosted domain names and has more information available here.

Multiple organizations with domain names registered under Network Solutions suffered problems with their domain names today, as their DNS nameservers were replaced with nameservers at ztomy.com. The nameservers at ztomy.com were configured to reply to DNS requests for the affected domains with IP addresses in the range 204.11.56.0/24. Cisco observed a large number of requests directed at these confluence-network IP addresses. Nearly 5000 domains may have been affected based on passive DNS data for those IPs.

Traffic hits to 204.11.56.0/24

Traffic hits to 204.11.56.0/24

Hijacking of a domain name’s DNS records is one of the worst attacks an organization can suffer. You literally have lost control over your domain.  Network Solutions, having been the original registrar for .com, .net, and .org domain names, is quite an attractive target for attackers. Originally it was unclear whether the issue was the result of an attack or a misconfiguration. It turns out the problem was both attack-related and also the result of a misconfiguration. Network Solutions issued a statement claiming, “In the process of resolving a Distributed Denial of Service (DDoS) incident on Wednesday night, the websites of a small number of Network Solutions customers were inadvertently affected for up to several hours.”

Interestingly, several of these domains were setup under different nameservers at ztomy.com. For example, the domain usps.com was pointed to the DNS nameservers ns1621.ztomy.com and ns2621.ztomy.com. Yelp had their nameservers changed to ns1620.ztomy.com and ns2620.ztomy.com. Fidelity, meanwhile, was pointed at ns1622.ztomy.com and ns2622.ztomy.com. However, the fact that so many domains were displaced in such a highly visible way supports Network Solutions’ claim that this was indeed a configuration error.

TRAC recommends anyone who has a domain registered with Network Solutions verify that their DNS nameservers are pointed at the correct location. TRAC also recommends network administrators check the logs from their network devices for connections to the 204.11.56.0/24 subnet. Organizations need to carefully consider how they would swiftly identify unauthorized modifications to their DNS records and how they would react to such a situation.

 

References

http://www.networksolutions.com/blog/2013/06/important-update-for-network-solutions-customers-experiencing-website-issues/

 

Thank you to Henry Stern, Martin Lee, Mary Landesman and Gregg Conklin for their assistance writing this post.

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

45 Comments.


  1. An impressive share! I have just forwarded this onto a friend who was doing a little research on
    this. And he actually bought me dinner due to
    the fact that I stumbled upon it for him… lol. So allow me to reword this.

    … Thank YOU for the meal!! But yeah, thanks for spending the
    time to talk about this issue here on your internet site.

       0 likes

  2. The configuration change for these domains such as fidelity.com and linked in.com does not look like a configuration error, but looks more like a deliberate configuration done by Network Solutions – perhaps while they were recovering from an attack. The various nameservers (and webservers) at ztomy.com IP space of 204.11.56.0/24 seem to be configured to answer mostly correct DNS responses to these domains (see below). Perhaps it is distributed anycast network such as cloud services providers. The network 204.11.56.0/23 seems to fit this criteria.

    # nslookup http://www.linkedin.com ns1621.ztomy.com
    Server: ns1621.ztomy.com
    Address: 204.11.56.21#53

    http://www.linkedin.com canonical name = la.linkedin.com.

       0 likes

  3. I live constantly on resolving the problem on my dns Hi pls

       0 likes

  4. Looks like you’ll have some more pretty graphs for us…NS is having major issues again today. A great way to start the morning…I had a new article to post!

       1 like

    • I can confirm… I don’t know what they’re doing to solve it, but I suddenly found a space between the host part and the domain name in our DNS console for all our A records… All domains we have that depend on networksolutions have problems. Domains registered somewhere else work fine.

         0 likes

  5. Indeed. I have 2 sites down this morning on NS.

       1 like

  6. We are also experiencing ADNS issues from Network Solutions. I have called and they acknowledged the outage but didn’t say what it was from.

    We have about 12 sites out.

       0 likes

  7. Same here. July 17th 2013, and our website which has its domain name registered through Networksolutions, is unreachable due to DNS errors (access is fine direct to its IP address). I thought that using a large and VERY expensive service like NeSol that we would avoid these issues. Now if I could just work out what to do about it?

       0 likes

    • There’s not much that can really be done about it as moving from one DNS server to another will require you logging into Network Solutions to change it. :(

      I also registered with the original and the biggest for the same reason–reliability. And to be honest, I’ve only had two outages (including this one) in about 9 years, so it’s not too bad. Especially when you look at the names of other companies who are with us in this outage.

         0 likes

  8. I’m also suffering from the loss of all DNS entries hosted by Network Solutions. And the main NS site is not responding so no way to admin any changes.

       0 likes

  9. We too are experiencing outages on all our site because nameservers are down. Unfortunately they are registered with Network Solutions..

    What’s really bad is the fact that there’s no communication or a status update, and how come such a massive internet player does not have a business continuity plan in place.

       2 likes

  10. Mister Houdini

    We have a dozen domain names with Network Solutions and virtually all of them have DNS problems today.

       0 likes

  11. Same here

       0 likes

  12. My NS email sites just came back up. Lets hope they stay up!

       1 like

  13. Hallmark Specialty

    I guess this should be our cue to switch DNS servers…

       0 likes

    • I wouldn’t change, and I personally won’t be changing. I’ve had almost zero problems for a decade with them. I can take a few hours of downtime every few decades, lol.

         0 likes

      • Mister Houdini

        Nearly 2 decades here. But I’ve had more problems in the past 2 years than the first 15.

        From Wikipedia: In August 2011, it was announced that Network Solutions will be bought by Web.com for $405 million and 18 million shares. On October 27, 2011, Web.com announced the completion of the Network Solutions acquisition. This was immediately followed by the departure of CEO Tim Kelly and other key leadership. Large scale employee layoffs began the following day. By December 31, 2011, over half of the office space in the Herndon, VA based headquarters had been vacated and returned to the property management. On March 31, 2012, the company’s Belleville, Illinois office was closed.

           0 likes

        • All the major players leaving a company is never a good sign. Jelsoft underwent the same problem when they were bought out by Internet Brands. Except, IB didn’t completely level the office. :o

             0 likes

  14. Same here, but seems only to be sites hosted by Network Solutions. Those hosted elsewhere are fine. Ah! Their own site is back up at 10:52 a.m. EDT, so maybe they’ve fixed it. Saw a notice on their site yesterday that advised they will be down for maintenance tomorrow night, so this could be related in some way.

       0 likes

  15. Same here, but only wordpress-based sites were affected. the hack page. Some hgroup calling themselves Islamic Ghosts Team took cred on the hack page. I was able to FTP in and changed filenames that were dated since yesterday morning to recover web access. Found a gif plant named animated-messages-small2.gif that redirected to89.144.57.86. I posted the hack replacement page’s header scripts if anyone is interested at http://www.galactickegger.com.

       2 likes

    • Ummm…I don’t think you’re experiencing the same problems as us.

      To put it another way:
      “these aren’t the droids you’re looking for…”

         0 likes

  16. Then perhaps there were coordinated attacks on multiple fronts using multiple methods. Some Netsol WordPress sites got hacked last month; and of all the sites we have registered with them only pure WP sites were hacked yesterday. I’m not here to compare tool bags … I’m here to report what I found. My apologies if featyhers were ruffled.

       0 likes

    • Mister Houdini

      I looked at your page… At least you’ve still got a sense of humor. “…islamic ghost limpdick society…” LMAO

         0 likes

    • No harm, no foul. I didn’t know if you were legit or some spammer trying to drive traffic to their site. :) At least you gave me a good excuse to use a Star Wars line. :D

      You may definitely be on to something though as both of these outages seem to happen in the same timeframe. Where did those attacks originate from?

         0 likes

    • I don’t think it was limited to wordpress. I have a site on one of Network Solution’s shared JSP servers (*.netsoljsp.com), and on Tuesday night (7/16) a few of my users were redirected to Islamic Ghost pages instead.

         0 likes

  17. Thank you!

       0 likes

  18. No worries mate. I xfer’d from the department of redundancy department, so BUs are in place. Just can’t access email … manure occurs. Cheers!

       0 likes

    • Backups are always a good idea. :) Glad to hear it’s not affecting you much. :D

      If it was truly multi-prong like we’re theorizing, it was probably distributed geo-locally and will have IPs from all over the world. :(

         0 likes

  19. Farthest I was able to trace was 89.144.57.86 (Isp4p IT Services in Ludwigshafen Germany.)

       0 likes

  20. And Cisco adds a statement at the top of this article as numerous tweets and tech360.com erronously report this article as happening today. :O
    http://www.techzone360.com/topics/techzone/articles/2013/07/17/345902-network-solutions-experiences-hijacking-dns-records.htm

    I don’t which is worse, reporting wrong bad news or the outage itself, lol.

       0 likes

  21. We had several customers using network solutions with issues today.

    I’ve seen intermittent emails being rejected with error “451 Temporary local problem – please try later”.

    Issue seems to be fully resolved now.

       0 likes

  22. Mister Houdini

    Cisco has a new blog post about July 16/17 issues here http://blogs.cisco.com/security/network-solutions-customer-site-compromises-and-ddos/

       0 likes

  23. Fantastic issues altogether, you simply gained a new reader. What may you suggest about your submit that you simply made a few days in the past? Any sure?

       0 likes

  24. An impressive share! thanks for spending the
    time to talk about this issue here on your internet site.

       0 likes

  25. Thank you!

       0 likes

  26. So, um, if I am not being impertinent, please do tell me just who in the f**k is ZTOMY.COM?

    I mean are they criminals, or what? What is their scam? Is it just another front for just another online business that will do anything, legal or illegal, to get clicks?

    The WHOIS record is obfsucated, and nobody seems to be saying anything about just who the hell these people are… not Network Solutions, not Akami (who is giving that domain its base DNS), and apparently not Cisco either.

    C’mon. Why is everybody so shy?

       1 like

  1. Return to Countries/Regions
  2. Return to Home
  1. All Security
  2. Return to Home