On Thu, 23 Mar 2000, Nick Bastin wrote:
I can ping all of them, but none answer DNS queries. Makes it tough to access their customers.
Sprint has a master ticket #3461302 open for at least something related to this problem, or at least that's what the engineer thought. Apparently they're having an 'issue' with a router on the east coast. He muttered something about gateway 13, but I didn't catch it all.
I just got another call back to tell me that they'd isolated the problem to the Orlando, FL site where we connect to them. I said "I don't think so." All their NS servers are unreachable or unresponsive (to the whole net, not just me), and they think it's a bad circuit in Orlando? It seems almost like the two callbacks I've gotten so far are from different parts of Sprint. Neither seems to know what the other is doing. Neither seems to know what's going on in general. At least the first one knew there was some general "big problem" on their network. Both are acting on the same ticket opened by a single phone call from me.
Probably a good sign - their name servers are responding again. traceroute's still die though. ; <<>> DiG 8.2 <<>> @206.228.179.10 sprint.com any any ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 7 ;; QUERY SECTION: ;; sprint.com, type = ANY, class = ANY <actual reply deleted to save space> ;; Total query time: 44 msec ;; FROM: rwstevens to SERVER: 206.228.179.10 ;; WHEN: Thu Mar 23 00:46:18 2000 ;; MSG SIZE sent: 28 rcvd: 402 -- Nick Bastin Software Developer OPNET Technologies