Also reporting the same, we saw this get really bad a little before 2:00 AM America/Chicago, and recover around 4:20.
> On Nov 24, 2014, at 4:50 AM, Stephane Bortzmeyer via Outages > <[email protected]> wrote: > > On Mon, Nov 24, 2014 at 10:09:14AM +0000, > Dylan Ebner via Outages <[email protected]> wrote > a message of 537 lines which said: > >> networksolutions.com also does not resolve on comcast or CL dns >> servers. It does resolve on google dns servers but it is not >> accessable. > > This domain name has three name servers but all of them have the same > IP address! > > % check-soa -i networksolutions.com > ns1.netsol.com. > 209.17.114.135: OK: 2014103001 (19 ms) > ns2.netsol.com. > 209.17.114.135: OK: 2014103001 (20 ms) > ns3.netsol.com. > 209.17.114.135: OK: 2014103001 (20 ms) > > So, any IP problem (routing, filtering, whatever) will take them down > at the same time. > > What to add? It is Network Solutions. The gods themselves cannot make > them professionnal. > >> COMCAST DNS SERVERS: DOES NOT WORK >>> server 75.75.76.76 >> Default Server: cdns02.comcast.net<http://cdns02.comcast.net/> >> Address: 75.75.76.76 > > By the way, nslookup is a poor DNS debugging tool. > > _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
