Posted on 04/04/2006 6:59:52 AM PDT by LesbianThespianGymnasticMidget
DNS seems hosed all over. Looks like a router went down close to the DNS root for .com. Traceroute is showing 100% loss at router Defender-1, and I am seeing lots of problems.
http://www.networksolutions.com
When did this start?
What does this mean?
Oh boy. This does look series, as a quick check shows lookups timing out for about 40% of the .com sites we tried to randomnly reached...
15 to 18 minutes ago...
Half my emails went out and then poof.
Means half the internet is broken, in a nutshell.
and with the 45 minute cascade, does it mean we are going to lose 100% of the dns for .com in another 20 minutes?
So this means a brief respite from spam, I guess. Glad the FR IP address is cached in my browser!
traceroute just went through. looks like it may be fixed.
Don't know if this is related, but The net was real slow last night. Fixed itself this morning.
Looks fixed here. A lookup failure earlier worked now.
I have no idea on future loss of "visbility". For us, we had problems getting to around 40% of the .com sites we randomly tried. Sites that I know are served by NetSol DNS Servers are not reachable...
Looks fixed from everywhere I tried (Colorado/Virginia/Indiana/California) and they all failed 10 minutes ago.
Now some things are coming back. So looks like NetSol et al are on top of this...
Thank God..... I was not looking forward to taking calls on this and trying to "splain it is not my fault"
For peoples enjoyment:
Flat out broken
I have a site with them. My pages were serving OK- but my MySQL forum was out for a couple of hours. No explantion yet.
It was for about an hour. All networks solutions servers were unreachable, and since lots of people use their name servers as primaries, lots of sites were unreachable. It looked like a router was down. Once they got it fixed, no more problems.
40% of .com domains being unresolvable via DNS qualifies as lots of problems. Email servers puking because of the DNS problems also qualifies as lots of problems. Think about 40% of the mx records for .com domains not being there, and how mail servers react. It was a PITA, and I am just glad it got fixed quickly. (An hour to switch out a backbone level router qualifies as damned quickly.)
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.