  Anonymous_ Anonymous Premium join:2004-06-21 127.0.0.1 clubs:
·RoadRunner Cable
·Time Warner Cable
·Time Warner VOIP
4 edits | [TWC] DNS outage Los angeles Part 2 (Comfirmed outage)
DNS look up times out once again i bet they are applying the update
|
|
  Anonymous_ Anonymous Premium join:2004-06-21 127.0.0.1 clubs:
·RoadRunner Cable
·Time Warner Cable
·Time Warner VOIP
1 edit | Re: [TWC] DNS outage Los angeles Part 2 (Comfirmed outage)
Comfirmed outage
changeing DNS to 4.2.2.2
C:\Documents and Settings\Administrator>nslookup dslreports.com Server: DD-WRT Address: 192.168.1.1
DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to DD-WRT timed-out
C:\Documents and Settings\Administrator>nslookup dslreports.com Server: DD-WRT Address: 192.168.1.1
DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to DD-WRT timed-out
C:\Documents and Settings\Administrator>nslookup dslreports.com Server: DD-WRT Address: 192.168.1.1
after change to 4.2.2.2
Non-authoritative answer: Name: dslreports.com Address: 209.123.109.175
C:\Documents and Settings\Administrator> |
|
  amysheehan Premium,VIP,MVM join:1999-12-21 Huntington Beach, CA 1 edit | reply to Anonymous_ Re: [TWC] DNS outage Los angeles 3 AM
It has been up and down for the past 2 hours or so
Mail from rr and dslr still time out tho -amy- |
|
  Anonymous_ Anonymous Premium join:2004-06-21 127.0.0.1 clubs: | the upload blows i am only getting 280k to the east cost
packets are over lapping |
|
  lordpuffer I Was Very Drunk At The Time Premium join:2004-09-19 West Hollywood, CA | Talked to Tier 3 Tech Support......Tech said they did make the DNS change. Said that there should be no other problems, but obviously there are some. -- "That Which Does Not Kill Me Makes Me Stronger"! |
|
  Anonymous_ Anonymous Premium join:2004-06-21 127.0.0.1 clubs: | 66.75.164.90 (dns-cac-lb-01.orange.rr.com) appears to have POOR source port randomness and GREAT transaction ID randomness.
unpatched.... |
|
  MacLeech The one and only Premium join:2001-07-14 SoCal
4 edits | reply to Anonymous_ Re: [TWC] DNS outage Los angeles Part 2 (Comfirmed outage)
 DNS server failure, first around 11pm local then around 3-4am local |
Obviously RR sucks for letting the DNS servers go down AGAIN.
It was during the change management period so it was possible it was a deliberate change though. If it was a change management, multiple servers should allow for changes on individual servers while letting the others handle traffic... but maybe it was something bigger not directly involving patching the DNS servers.
Great reason to use Dnsmasq within your router to add more DNS servers... multiple provider redundancy is such a simple thing for the end user.
P.S. It should be up and running again. Graph from here (times on graph are 3 hours ahead): »/testhistory?v···n=ec&p=2 |
|
 shyguy907
join:2007-02-02 Torrance, CA 2 edits | reply to Anonymous_ Re: [TWC] DNS outage Los angeles Part 2 (Comfirmed outage)
I got timed out on all websites, around 3AM. Now everything seems to be working fine. |
|
  amysheehan Premium,VIP,MVM join:1999-12-21 Huntington Beach, CA
·RoadRunner Cable
| reply to MacLeech Re: [TWC] DNS outage Los angeles Part 2 (Comfirmed outage)
 East Coast |  West |
Here are my East and West Coast monitors from last 24 hours.
Looks like not every SoCal user was affected [ of those who are monitored ]
-amy- -- Proud Member of ASAP DSLR Phishtracker |
|
  MacLeech The one and only Premium join:2001-07-14 SoCal
| said by amysheehan :Looks like not every SoCal user was affected [ of those who are monitored ] Individual users should NOT have seen packet loss on their monitors for their own IPs. This was a DNS outage, so their modem would be working fine, they just couldn't resolve any site names.
The monitor pic I posted was for the one I setup for a random SoCal RR DNS server. |
|
 Mele20 Premium join:2001-06-05 Hilo, HI
| I had a DNS outage here in Hawaii Sunday evening at slightly before 8PM (11PM in California). My first thought was OMG, Orange is patching the DNS servers and evidently they are patching the two at Oceanic also (as well as our third one which is at Orange). I could access the modem's web page but nothing else. I called Oceanic and got a tier 1 person who had never heard of DNS servers, had no idea about any security issues with them and need for patching, etc.
The tier 1 person checked my modem and said everything was fine with the modem so if I couldn't reach websites then I must have a computer problem and she started to transfer me to NHD! I insisted this was a DNS problem and likely related to patching and told her I needed to speak to tier 3. She transferred me then to tier 3 and I got into a long hold time. After 20 minutes on hold, I decided to recyle the modem and router and reboot and after that I was able to again reach web sites and use Ping Plotter. I wonder if my problem was because it was Sunday evening at 8PM which is Hawaii's heaviest use of the internet and the Oceanic DNS servers were busy so I got routed to the Orange backup one 66.75.160.63 that was down.
I just wish we would get patched. I don't know if Oceanic will do the patching for our two DNS servers, and Orange for the backup one there, or what. It is making me very nervous. -- "The same ferocity that our founders devoted to protect the freedom and independence of the press is now appropriate for our defense of the freedom of the internet. The stakes are the same: the survival of our Republic". Al Gore, The Assault on Reason |
|