
Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive? Take this for example: AMERIGON.COM has name server entries NS9.WORLDNIC.COM and NS10.WORLDNIC.COM... $ dig @ns9.worldnic.com amerigon.com ; <<>> DiG 9.8.1-P1 <<>> @ns9.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig @ns10.worldnic.com amerigon.com ; <<>> DiG 9.8.1-P1 <<>> @ns10.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached

Now more of our sites are starting to fail as the local DNS cache begins to expire. This could be affecting everyone who uses NetSol for name resolution, or at least a large cross-section of their user base. On Wed, Jul 17, 2013 at 9:31 AM, Mike Phipps <plstate@gmail.com> wrote:
Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive? Take this for example:
AMERIGON.COM has name server entries NS9.WORLDNIC.COM and NS10.WORLDNIC.COM...
$ dig @ns9.worldnic.com amerigon.com
; <<>> DiG 9.8.1-P1 <<>> @ns9.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
$ dig @ns10.worldnic.com amerigon.com
; <<>> DiG 9.8.1-P1 <<>> @ns10.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached

NetSol name servers are unreachable here as well, and we're also seeing failures. ----- Original Message ----- From: "Mike Phipps" <plstate@gmail.com> To: Outages@outages.org Sent: Wednesday, July 17, 2013 6:48:41 AM Subject: Re: [outages] Network Solutions DNS Stuffed? Now more of our sites are starting to fail as the local DNS cache begins to expire. This could be affecting everyone who uses NetSol for name resolution, or at least a large cross-section of their user base. On Wed, Jul 17, 2013 at 9:31 AM, Mike Phipps < plstate@gmail.com > wrote: Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive? Take this for example: AMERIGON.COM has name server entries NS9.WORLDNIC.COM and NS10.WORLDNIC.COM... $ dig @ ns9.worldnic.com amerigon.com ; <<>> DiG 9.8.1-P1 <<>> @ ns9.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig @ ns10.worldnic.com amerigon.com ; <<>> DiG 9.8.1-P1 <<>> @ ns10.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

http://blogs.cisco.com/security/hijacking-of-dns-records-from-network-soluti... Pretty much affecting every website that uses Network Solutions for DNS.

Apologies - was following tweets and didn't see the date on this. On 7/17/2013 9:43 AM, Rory McCann wrote:
http://blogs.cisco.com/security/hijacking-of-dns-records-from-network-soluti...
Pretty much affecting every website that uses Network Solutions for DNS.

That wasn't today :) - Jared On Jul 17, 2013, at 10:43 AM, Rory McCann <rmm.lists@gmail.com> wrote:
http://blogs.cisco.com/security/hijacking-of-dns-records-from-network-soluti...
Pretty much affecting every website that uses Network Solutions for DNS. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

We're seeing the same thing here, plus the NetSol website appears down. Appears to be across multiple NS servers and not just 43/44. C:\Users\dpratho\Tools\dig>dig @ns47.worldnic.com www.veci.com ; <<>> DiG 9.3.2 <<>> @ns47.worldnic.com www.veci.com ; (1 server found) ;; global options: printcmd ;; connection timed out; no servers could be reached

Yes the site is down and some of the World NIC DNS servers I reported to outages.org site a while ago, guess they are napping From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Mike Phipps Sent: Wednesday, July 17, 2013 8:49 AM To: Outages@outages.org Subject: Re: [outages] Network Solutions DNS Stuffed? Now more of our sites are starting to fail as the local DNS cache begins to expire. This could be affecting everyone who uses NetSol for name resolution, or at least a large cross-section of their user base. On Wed, Jul 17, 2013 at 9:31 AM, Mike Phipps <plstate@gmail.com<mailto:plstate@gmail.com>> wrote: Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive? Take this for example: AMERIGON.COM<http://AMERIGON.COM> has name server entries NS9.WORLDNIC.COM<http://NS9.WORLDNIC.COM> and NS10.WORLDNIC.COM... $ dig @ns9.worldnic.com<http://ns9.worldnic.com> amerigon.com<http://amerigon.com> ; <<>> DiG 9.8.1-P1 <<>> @ns9.worldnic.com<http://ns9.worldnic.com> amerigon.com<http://amerigon.com> ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig @ns10.worldnic.com<http://ns10.worldnic.com> amerigon.com<http://amerigon.com> ; <<>> DiG 9.8.1-P1 <<>> @ns10.worldnic.com<http://ns10.worldnic.com> amerigon.com<http://amerigon.com> ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached

On Wed, 17 Jul 2013, Mike Phipps wrote:
Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive?
Yup, just noticed this for a few sites (groceryiq.com is one of them); the ones I'm seeing use ns43.worldnic.com/ns44.worldnic.com.

It just started resolving my domains. On Jul 17, 2013, at 9:57 AM, Nate Carlson <nanog@natecarlson.com> wrote:
On Wed, 17 Jul 2013, Mike Phipps wrote:
Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive?
Yup, just noticed this for a few sites (groceryiq.com is one of them); the ones I'm seeing use ns43.worldnic.com/ns44.worldnic.com. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

On Wed, Jul 17, 2013 at 09:31:33AM -0400, Mike Phipps wrote:
Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive? Take this for example:
AMERIGON.COM has name server entries NS9.WORLDNIC.COM and NS10.WORLDNIC.COM...
$ dig @ns9.worldnic.com amerigon.com
; <<>> DiG 9.8.1-P1 <<>> @ns9.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
$ dig @ns10.worldnic.com amerigon.com
; <<>> DiG 9.8.1-P1 <<>> @ns10.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
Can confirm this from my Comcast residential connection in Mountain View, CA. Other types of queries (NS, SOA, etc.) result in the same behaviour. Also just for the record: ns9.worldnic.com has address 205.178.190.5 ns10.worldnic.com has address 206.188.198.5 traceroutes/mtrs to these destinations stop presumably at a border router -- this will vary based on source location, but for me trying to reach ns9 stops at hr1-tengig-2-0-0.sterling2dc2.savvis.net, ns10 stops at ae-1-51.edge4.Atlanta2.Level3.net. So possibilities include issues with NetSol, or return path issues (which I obviously cannot confirm). -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB |

Yes, around 09:43 we saw DNS resolution drop off for some domains we monitor. Name Server: NS45.WORLDNIC.COM Name Server: NS46.WORLDNIC.COM Name Server: NS63.WORLDNIC.COM Name Server: NS64.WORLDNIC.COM From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Mike Phipps Sent: Wednesday, July 17, 2013 9:32 AM To: Outages@outages.org Subject: [outages] Network Solutions DNS Stuffed? Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive? Take this for example: AMERIGON.COM<http://AMERIGON.COM> has name server entries NS9.WORLDNIC.COM<http://NS9.WORLDNIC.COM> and NS10.WORLDNIC.COM... $ dig @ns9.worldnic.com<http://ns9.worldnic.com> amerigon.com<http://amerigon.com> ; <<>> DiG 9.8.1-P1 <<>> @ns9.worldnic.com<http://ns9.worldnic.com> amerigon.com<http://amerigon.com> ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig @ns10.worldnic.com<http://ns10.worldnic.com> amerigon.com<http://amerigon.com> ; <<>> DiG 9.8.1-P1 <<>> @ns10.worldnic.com<http://ns10.worldnic.com> amerigon.com<http://amerigon.com> ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached

Seeing the same thing from here for NS1 and NS2- 07/17/13 09:53:00 dig ns72.worldnic.com @ ns71.worldnic.com Dig ns72.worldnic.com@ns71.worldnic.com (205.178.190.36) ... failed, couldn't connect to nameserver 07/17/13 09:54:28 dig ns72.worldnic.com @ ns72.worldnic.com Dig ns72.worldnic.com@ns72.worldnic.com (206.188.198.36) ... Non-authoritative answer Nameserver has a problem and can't talk right now Netsol website is very slow but makes no mention of any problems. trying to open a ticket, but I'm sure they know... Kevin Dougherty VP Technology Inner Traditions International One Park Street Rochester, VT 05767 802-767-3174 x130 On 7/17/2013 9:31 AM, Mike Phipps wrote:
Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive? Take this for example:
AMERIGON.COM <http://AMERIGON.COM> has name server entries NS9.WORLDNIC.COM <http://NS9.WORLDNIC.COM> and NS10.WORLDNIC.COM...
$ dig @ns9.worldnic.com <http://ns9.worldnic.com> amerigon.com <http://amerigon.com>
; <<>> DiG 9.8.1-P1 <<>> @ns9.worldnic.com <http://ns9.worldnic.com> amerigon.com <http://amerigon.com> ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
$ dig @ns10.worldnic.com <http://ns10.worldnic.com> amerigon.com <http://amerigon.com>
; <<>> DiG 9.8.1-P1 <<>> @ns10.worldnic.com <http://ns10.worldnic.com> amerigon.com <http://amerigon.com> ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

If you call their hotline you will get a short msg saying they are aware of the issue? No details:( (coffee != sleep) & (!coffee == sleep) Donald.Smith@centurylink.com<mailto:Donald.Smith@centurylink.com> ________________________________ From: Outages [outages-bounces@outages.org] on behalf of Kevin Dougherty [kevind@innertraditions.com] Sent: Wednesday, July 17, 2013 8:04 AM To: outages@outages.org Subject: Re: [outages] Network Solutions DNS Stuffed? Seeing the same thing from here for NS1 and NS2- 07/17/13 09:53:00 dig ns72.worldnic.com @ ns71.worldnic.com Dig ns72.worldnic.com@ns71.worldnic.com<mailto:ns72.worldnic.com@ns71.worldnic.com> (205.178.190.36) ... failed, couldn't connect to nameserver 07/17/13 09:54:28 dig ns72.worldnic.com @ ns72.worldnic.com Dig ns72.worldnic.com@ns72.worldnic.com<mailto:ns72.worldnic.com@ns72.worldnic.com> (206.188.198.36) ... Non-authoritative answer Nameserver has a problem and can't talk right now Netsol website is very slow but makes no mention of any problems. trying to open a ticket, but I'm sure they know... Kevin Dougherty VP Technology Inner Traditions International One Park Street Rochester, VT 05767 802-767-3174 x130 On 7/17/2013 9:31 AM, Mike Phipps wrote: Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive? Take this for example: AMERIGON.COM<http://AMERIGON.COM> has name server entries NS9.WORLDNIC.COM<http://NS9.WORLDNIC.COM> and NS10.WORLDNIC.COM... $ dig @ns9.worldnic.com<http://ns9.worldnic.com> amerigon.com<http://amerigon.com> ; <<>> DiG 9.8.1-P1 <<>> @ns9.worldnic.com<http://ns9.worldnic.com> amerigon.com<http://amerigon.com> ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig @ns10.worldnic.com<http://ns10.worldnic.com> amerigon.com<http://amerigon.com> ; <<>> DiG 9.8.1-P1 <<>> @ns10.worldnic.com<http://ns10.worldnic.com> amerigon.com<http://amerigon.com> ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages

I am seeing this as well, cant get to the site, customers who have their dns with them are not resolving On Wed, Jul 17, 2013 at 9:31 AM, Mike Phipps <plstate@gmail.com> wrote:
Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive? Take this for example:
AMERIGON.COM has name server entries NS9.WORLDNIC.COM and NS10.WORLDNIC.COM...
$ dig @ns9.worldnic.com amerigon.com
; <<>> DiG 9.8.1-P1 <<>> @ns9.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
$ dig @ns10.worldnic.com amerigon.com
; <<>> DiG 9.8.1-P1 <<>> @ns10.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

I can confirm, perhaps this will also help? $ dig @ns9.worldnic.com amerigon.com ; <<>> DiG 9.9.2-P1 <<>> @ns9.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached [same result for ns10] ------ $ traceroute ns9.worldnic.com traceroute to ns9.worldnic.com (205.178.190.5), 30 hops max, 60 byte packets 1 gatekeeper.anthonyrhook.com (192.168.1.1) 0.155 ms 0.233 ms 0.321 ms 2 drr01.waus.wi.frontiernet.net (74.42.148.129) 33.632 ms 35.323 ms 36.750 ms 3 static-50-50-0-13.snpr.wi.frontiernet.net (50.50.0.13) 37.787 ms 39.193 ms 40.666 ms 4 xe--5-2-0---0.car01.waus.wi.frontiernet.net (74.40.4.25) 42.414 ms 43.639 ms 45.065 ms 5 xe--10-1-0---0.cor02.chcg.il.frontiernet.net (74.40.4.29) 58.344 ms 59.321 ms 61.221 ms 6 ae1---0.cbr01.chcg.il.frontiernet.net (74.40.4.142) 63.568 ms 43.951 ms 44.024 ms 7 ix-0-3-1-0.tcore2.CT8-Chicago.as6453.net (206.82.141.105) 49.703 ms 49.820 ms 50.184 ms 8 if-22-2.tcore1.CT8-Chicago.as6453.net (64.86.79.2) 50.317 ms 51.601 ms 52.768 ms 9 64.86.78.10 (64.86.78.10) 54.762 ms 56.500 ms 57.942 ms 10 cr2-tengig-0-5-3-0.chd.savvis.net (206.28.96.5) 62.620 ms 63.358 ms 64.576 ms 11 cr1-te-0-13-2-0.dck.savvis.net (204.70.200.90) 86.971 ms 87.690 ms 89.397 ms 12 hr1-tengig-2-0-0.sterling2dc2.savvis.net (204.70.197.74) 67.463 ms 67.602 ms 68.783 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * *^C On Wed, Jul 17, 2013 at 8:31 AM, Mike Phipps <plstate@gmail.com> wrote:
Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive? Take this for example:
AMERIGON.COM has name server entries NS9.WORLDNIC.COM and NS10.WORLDNIC.COM...
$ dig @ns9.worldnic.com amerigon.com
; <<>> DiG 9.8.1-P1 <<>> @ns9.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
$ dig @ns10.worldnic.com amerigon.com
; <<>> DiG 9.8.1-P1 <<>> @ns10.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- - Anthony Hook

More here: https://www.facebook.com/networksolutions https://www.networksolutions.com/blog/2013/07/notice-to-customers-who-may-be... (I can’t currently load that page) Frank From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Anthony Hook Sent: Wednesday, July 17, 2013 9:13 AM To: Mike Phipps Cc: OUTAGES Mailing List Subject: Re: [outages] Network Solutions DNS Stuffed? I can confirm, perhaps this will also help? $ dig @ns9.worldnic.com <http://ns9.worldnic.com> amerigon.com <http://amerigon.com> ; <<>> DiG 9.9.2-P1 <<>> @ns9.worldnic.com <http://ns9.worldnic.com> amerigon.com <http://amerigon.com> ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached [same result for ns10] ------ $ traceroute ns9.worldnic.com <http://ns9.worldnic.com> traceroute to ns9.worldnic.com <http://ns9.worldnic.com> (205.178.190.5), 30 hops max, 60 byte packets 1 gatekeeper.anthonyrhook.com <http://gatekeeper.anthonyrhook.com> (192.168.1.1) 0.155 ms 0.233 ms 0.321 ms 2 drr01.waus.wi.frontiernet.net <http://drr01.waus.wi.frontiernet.net> (74.42.148.129) 33.632 ms 35.323 ms 36.750 ms 3 static-50-50-0-13.snpr.wi.frontiernet.net <http://static-50-50-0-13.snpr.wi.frontiernet.net> (50.50.0.13) 37.787 ms 39.193 ms 40.666 ms 4 xe--5-2-0---0.car01.waus.wi.frontiernet.net <http://xe--5-2-0---0.car01.waus.wi.frontiernet.net> (74.40.4.25) 42.414 ms 43.639 ms 45.065 ms 5 xe--10-1-0---0.cor02.chcg.il.frontiernet.net <http://xe--10-1-0---0.cor02.chcg.il.frontiernet.net> (74.40.4.29) 58.344 ms 59.321 ms 61.221 ms 6 ae1---0.cbr01.chcg.il.frontiernet.net <http://ae1---0.cbr01.chcg.il.frontiernet.net> (74.40.4.142) 63.568 ms 43.951 ms 44.024 ms 7 ix-0-3-1-0.tcore2.CT8-Chicago.as6453.net <http://ix-0-3-1-0.tcore2.CT8-Chicago.as6453.net> (206.82.141.105) 49.703 ms 49.820 ms 50.184 ms 8 if-22-2.tcore1.CT8-Chicago.as6453.net <http://if-22-2.tcore1.CT8-Chicago.as6453.net> (64.86.79.2) 50.317 ms 51.601 ms 52.768 ms 9 64.86.78.10 (64.86.78.10) 54.762 ms 56.500 ms 57.942 ms 10 cr2-tengig-0-5-3-0.chd.savvis.net <http://cr2-tengig-0-5-3-0.chd.savvis.net> (206.28.96.5) 62.620 ms 63.358 ms 64.576 ms 11 cr1-te-0-13-2-0.dck.savvis.net <http://cr1-te-0-13-2-0.dck.savvis.net> (204.70.200.90) 86.971 ms 87.690 ms 89.397 ms 12 hr1-tengig-2-0-0.sterling2dc2.savvis.net <http://hr1-tengig-2-0-0.sterling2dc2.savvis.net> (204.70.197.74) 67.463 ms 67.602 ms 68.783 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * *^C On Wed, Jul 17, 2013 at 8:31 AM, Mike Phipps <plstate@gmail.com <mailto:plstate@gmail.com> > wrote: Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive? Take this for example: AMERIGON.COM <http://AMERIGON.COM> has name server entries NS9.WORLDNIC.COM <http://NS9.WORLDNIC.COM> and NS10.WORLDNIC.COM... $ dig @ns9.worldnic.com <http://ns9.worldnic.com> amerigon.com <http://amerigon.com> ; <<>> DiG 9.8.1-P1 <<>> @ns9.worldnic.com <http://ns9.worldnic.com> amerigon.com <http://amerigon.com> ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig @ns10.worldnic.com <http://ns10.worldnic.com> amerigon.com <http://amerigon.com> ; <<>> DiG 9.8.1-P1 <<>> @ns10.worldnic.com <http://ns10.worldnic.com> amerigon.com <http://amerigon.com> ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached _______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages -- - Anthony Hook

Now posted on their facebook site: “Network Solutions is experiencing a Distributed Denial of Service (DDOS) attack that is impacting our customers as well as the Network Solutions site. Our technology team is working to mitigate the situation. Please check back for updates.” I don’t have their earlier posting talking about yesterday’s issues. I also learned from a co-worker (who supports some small banks) about yesterday’s issues that “It was an Islamic group. It sounded like servers were compromised, which lead to the compromised web sites.” He either learned this in a news article, or a banking-related security bulletin. Frank From: Frank Bulk (iname.com) [mailto:frnkblk@iname.com] Sent: Wednesday, July 17, 2013 9:53 AM To: 'Anthony Hook'; Mike Phipps Cc: OUTAGES Mailing List Subject: RE: [outages] Network Solutions DNS Stuffed? More here: https://www.facebook.com/networksolutions https://www.networksolutions.com/blog/2013/07/notice-to-customers-who-may-be... (I can’t currently load that page) Frank From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Anthony Hook Sent: Wednesday, July 17, 2013 9:13 AM To: Mike Phipps Cc: OUTAGES Mailing List Subject: Re: [outages] Network Solutions DNS Stuffed? I can confirm, perhaps this will also help? $ dig @ns9.worldnic.com <http://ns9.worldnic.com> amerigon.com <http://amerigon.com> ; <<>> DiG 9.9.2-P1 <<>> @ns9.worldnic.com <http://ns9.worldnic.com> amerigon.com <http://amerigon.com> ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached [same result for ns10] ------ $ traceroute ns9.worldnic.com <http://ns9.worldnic.com> traceroute to ns9.worldnic.com <http://ns9.worldnic.com> (205.178.190.5), 30 hops max, 60 byte packets 1 gatekeeper.anthonyrhook.com <http://gatekeeper.anthonyrhook.com> (192.168.1.1) 0.155 ms 0.233 ms 0.321 ms 2 drr01.waus.wi.frontiernet.net (74.42.148.129) 33.632 ms 35.323 ms 36.750 ms 3 static-50-50-0-13.snpr.wi.frontiernet.net <http://static-50-50-0-13.snpr.wi.frontiernet.net> (50.50.0.13) 37.787 ms 39.193 ms 40.666 ms 4 xe--5-2-0---0.car01.waus.wi.frontiernet.net <http://xe--5-2-0---0.car01.waus.wi.frontiernet.net> (74.40.4.25) 42.414 ms 43.639 ms 45.065 ms 5 xe--10-1-0---0.cor02.chcg.il.frontiernet.net <http://xe--10-1-0---0.cor02.chcg.il.frontiernet.net> (74.40.4.29) 58.344 ms 59.321 ms 61.221 ms 6 ae1---0.cbr01.chcg.il.frontiernet.net <http://ae1---0.cbr01.chcg.il.frontiernet.net> (74.40.4.142) 63.568 ms 43.951 ms 44.024 ms 7 ix-0-3-1-0.tcore2.CT8-Chicago.as6453.net <http://ix-0-3-1-0.tcore2.CT8-Chicago.as6453.net> (206.82.141.105) 49.703 ms 49.820 ms 50.184 ms 8 if-22-2.tcore1.CT8-Chicago.as6453.net <http://if-22-2.tcore1.CT8-Chicago.as6453.net> (64.86.79.2) 50.317 ms 51.601 ms 52.768 ms 9 64.86.78.10 (64.86.78.10) 54.762 ms 56.500 ms 57.942 ms 10 cr2-tengig-0-5-3-0.chd.savvis.net <http://cr2-tengig-0-5-3-0.chd.savvis.net> (206.28.96.5) 62.620 ms 63.358 ms 64.576 ms 11 cr1-te-0-13-2-0.dck.savvis.net <http://cr1-te-0-13-2-0.dck.savvis.net> (204.70.200.90) 86.971 ms 87.690 ms 89.397 ms 12 hr1-tengig-2-0-0.sterling2dc2.savvis.net <http://hr1-tengig-2-0-0.sterling2dc2.savvis.net> (204.70.197.74) 67.463 ms 67.602 ms 68.783 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * *^C On Wed, Jul 17, 2013 at 8:31 AM, Mike Phipps <plstate@gmail.com <mailto:plstate@gmail.com> > wrote: Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive? Take this for example: AMERIGON.COM <http://AMERIGON.COM> has name server entries NS9.WORLDNIC.COM <http://NS9.WORLDNIC.COM> and NS10.WORLDNIC.COM... $ dig @ns9.worldnic.com <http://ns9.worldnic.com> amerigon.com <http://amerigon.com> ; <<>> DiG 9.8.1-P1 <<>> @ns9.worldnic.com <http://ns9.worldnic.com> amerigon.com <http://amerigon.com> ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached $ dig @ns10.worldnic.com <http://ns10.worldnic.com> amerigon.com <http://amerigon.com> ; <<>> DiG 9.8.1-P1 <<>> @ns10.worldnic.com <http://ns10.worldnic.com> amerigon.com <http://amerigon.com> ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached _______________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages -- - Anthony Hook

http://www.reddit.com/r/sysadmin/comments/1ihfix/is_there_a_network_solution... http://www.reddit.com/r/sysadmin/comments/1ihff8/network_solutions_dns_down_... Side note: Aside from the OT threads that this site may usually produce, reddit is at times a much faster indicator of problems than a mailing list. ***Stefan On Wed, Jul 17, 2013 at 8:31 AM, Mike Phipps <plstate@gmail.com> wrote:
Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive? Take this for example:
AMERIGON.COM has name server entries NS9.WORLDNIC.COM and NS10.WORLDNIC.COM...
$ dig @ns9.worldnic.com amerigon.com
; <<>> DiG 9.8.1-P1 <<>> @ns9.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
$ dig @ns10.worldnic.com amerigon.com
; <<>> DiG 9.8.1-P1 <<>> @ns10.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

AMERIGON.COM has name server entries NS9.WORLDNIC.COM and NS10.WORLDNIC.COM...
$ dig @ns9.worldnic.com amerigon.com
We have seen it across many Network Solutions DNS servers clients are using. Specifically: ns10 and ns11 ns31 and ns32 ns53 and ns54 ns97 and ns98 I think there have been a few more, checking with staff, so wider spread than just a couple of their dns servers. -- Nevin Lyne -- Founder & Director of Technology -- Gippy's Internet Solutions, LLC. - Arcustech, LLC. -- http://gippy.net/ - http://arcustech.com/

yes. Network Solutions is down. http://www.isitdownrightnow.com/networksolutions.com.html#commentstop On Jul 17, 2013, at 9:31 AM, Mike Phipps <plstate@gmail.com> wrote:
Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive? Take this for example:
AMERIGON.COM has name server entries NS9.WORLDNIC.COM and NS10.WORLDNIC.COM...
$ dig @ns9.worldnic.com amerigon.com
; <<>> DiG 9.8.1-P1 <<>> @ns9.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
$ dig @ns10.worldnic.com amerigon.com
; <<>> DiG 9.8.1-P1 <<>> @ns10.worldnic.com amerigon.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

On Wed, Jul 17, 2013 at 09:31:33AM -0400, Mike Phipps <plstate@gmail.com> wrote a message of 63 lines which said:
Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive?
According to Twitter, you are right :-)
AMERIGON.COM has name server entries NS9.WORLDNIC.COM and NS10.WORLDNIC.COM...
A bit better now: % check-soa -i AMERIGON.COM ns10.worldnic.COM. 206.188.198.5: OK: 112080413 (137 ms) ns9.worldnic.COM. 205.178.190.5: ERROR: Timeout The Web site http://www.networksolutions.com/ seems down as well.

I have a friend in Engineering at NetSol and they confirm a DDoS attack. They are working on resolution. ------------------ Aubrey Wells Director | Network Services VocalCloud 888.305.3850 support@vocalcloud.com www.vocalcloud.com On Wed, Jul 17, 2013 at 10:31 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>wrote:
On Wed, Jul 17, 2013 at 09:31:33AM -0400, Mike Phipps <plstate@gmail.com> wrote a message of 63 lines which said:
Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive?
According to Twitter, you are right :-)
AMERIGON.COM has name server entries NS9.WORLDNIC.COM and NS10.WORLDNIC.COM...
A bit better now:
% check-soa -i AMERIGON.COM ns10.worldnic.COM. 206.188.198.5: OK: 112080413 (137 ms) ns9.worldnic.COM. 205.178.190.5: ERROR: Timeout
The Web site http://www.networksolutions.com/ seems down as well. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

On Wed, Jul 17, 2013 at 09:31:33AM -0400, Mike Phipps <plstate@gmail.com> wrote a message of 63 lines which said:
Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive?
NS is "in the midst of having multiple organizations that have registered their domains with the company hijacked", according to TechZone360: http://www.techzone360.com/topics/techzone/articles/2013/07/17/345902-networ... -- Jim Goltz <jgoltz@mail.nih.gov>

On Wed, Jul 17, 2013 at 03:28:35PM +0000, Goltz, Jim (NIH/CIT) [E] wrote:
On Wed, Jul 17, 2013 at 09:31:33AM -0400, Mike Phipps <plstate@gmail.com> wrote a message of 63 lines which said:
Hello all, has anyone else noticed that some of the Network Solutions name servers are unresponsive?
NS is "in the midst of having multiple organizations that have registered their domains with the company hijacked", according to TechZone360:
http://www.techzone360.com/topics/techzone/articles/2013/07/17/345902-networ...
Author of that blog post is reiterating what was said on June 20th (almost a month ago), implying it's happening again today yet there's no actual evidence of that. Reference: http://blogs.cisco.com/security/hijacking-of-dns-records-from-network-soluti... -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB |

On Wed, Jul 17, 2013 at 03:28:35PM +0000, Goltz, Jim (NIH/CIT) [E] <jgoltz@mail.nih.gov> wrote a message of 19 lines which said:
NS is "in the midst of having multiple organizations that have registered their domains with the company hijacked", according to TechZone360:
http://www.techzone360.com/topics/techzone/articles/2013/07/17/345902-networ...
No, no, no. This paper is, despite its date, about a month-old *other* problem, documented in <http://blogs.cisco.com/security/hijacking-of-dns-records-from-network-solutions/>. Bad copy. As usual, do not believe eveything you read on the Web.
participants (20)
-
Anthony Hook
-
Aubrey Wells
-
Brad Vogt
-
chris
-
Daryl Pratho
-
Frank Bulk (iname.com)
-
Goltz, Jim (NIH/CIT) [E]
-
Jared Mauch
-
Jeremy Chadwick
-
Ken Holden
-
Kevin Dougherty
-
Marco Prechel
-
Mike Phipps
-
Nate Carlson
-
Nevin Lyne
-
Ramey, James (Rick)
-
Rory McCann
-
Smith, Donald
-
Stefan
-
Stephane Bortzmeyer