<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><DIV>UltraDNS is having a DDOS attack at its San Jose and Palo Alto locations. No ETA yet <BR></DIV>
<DIV style="FONT-FAMILY: times new roman, new york, times, serif; FONT-SIZE: 12pt"><BR>
<DIV style="FONT-FAMILY: arial, helvetica, sans-serif; FONT-SIZE: 13px"><FONT size=2 face=Tahoma>
<HR SIZE=1>
<B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> dl <kokushibyou@gmail.com><BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> outages@outages.org<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Wed, December 23, 2009 5:24:13 PM<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [outages] ultradns issues? unable to resolve amazon.com<BR></FONT><BR>It looks like this is a West coast issue - resolving via DNS servers<BR>on the East coast does in fact return DNS for Amazon.<BR><BR>Sounds like theres some murmur on nanog about this too.<BR><BR>; <<>> DiG 9.6.0-APPLE-P2 <<>> <A href="http://amazon.com/" target=_blank>amazon.com</A> @ns1.nyc.pnap.net<BR>;; global options: +cmd<BR>;; Got answer:<BR>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20214<BR>;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 6, ADDITIONAL: 8<BR><BR>;; QUESTION SECTION:<BR>;amazon.com.
IN A<BR><BR>;; ANSWER SECTION:<BR>amazon.com. 60 IN A 72.21.210.250<BR>amazon.com. 60 IN A 72.21.207.65<BR>amazon.com. 60 IN A 207.171.166.252<BR><BR>- DL<BR><BR><BR>On Wed, Dec 23, 2009 at 17:08, dl <<A href="mailto:kokushibyou@gmail.com" ymailto="mailto:kokushibyou@gmail.com">kokushibyou@gmail.com</A>> wrote:<BR>> Seeing problems trying to reach amazon.com. Looks like the ultradns<BR>> name servers aren't responding? at least from here, and other external<BR>> dns servers I query can't seem to resolve amazon either.<BR>><BR>> Friend of mine still has some of their DNS in cache, and hardcoding<BR>> dns in
my hosts file allows me to hit Amazon without any issue. I was<BR>> surfing fine until my DNS flushed and couldn't re-resolve.<BR>><BR>> Anyone else seeing anything fun?<BR>><BR>> Looks like they might be coming back online - my trace is actually<BR>> making it to them now, sort of.<BR>><BR>> - DL<BR>><BR>> Host Loss% Snt<BR>> Last Avg Best Wrst StDev<BR>> 1. 192.168.0.1 0.0% 40<BR>> 0.5 0.5 0.4 0.6 0.0<BR>> 2. *censored* 0.0% 40
7.4 8.7 6.6 26.0 3.7<BR>> 3. *censored* 0.0% 40 5.3 5.8 4.6 9.8 1.0<BR>> 4. <A href="http://ge-6-11-440.car2.seattle1.level3.net/" target=_blank>ge-6-11-440.car2.Seattle1.Level3.net</A> 0.0% 39<BR>> 20.0 31.0 5.6 209.0 57.9<BR>> 5. <A href="http://ae-32-52.ebr2.seattle1.level3.net/" target=_blank>ae-32-52.ebr2.Seattle1.Level3.net</A> 0.0% 39<BR>> 7.3 12.0 5.1 35.3 6.1<BR>> 6. <A href="http://ae-1-100.ebr1.seattle1.level3.net/" target=_blank>ae-1-100.ebr1.Seattle1.Level3.net</A> 2.6%
39<BR>> 6.4 12.7 5.8 27.6 5.4<BR>> 7. <A href="http://ae-7.ebr2.sanjose1.level3.net/" target=_blank>ae-7.ebr2.SanJose1.Level3.net</A> 5.1% 39<BR>> 27.3 29.0 22.4 54.4 5.9<BR>> 8. <A href="http://ae-72-72.csw2.sanjose1.level3.net/" target=_blank>ae-72-72.csw2.SanJose1.Level3.net</A> 0.0% 39<BR>> 33.1 30.1 23.0 80.4 9.2<BR>> 9. <A href="http://ae-2-79.edge1.sanjose3.level3.net/" target=_blank>ae-2-79.edge1.SanJose3.Level3.net</A> 12.8% 39<BR>> 24.1 29.9 22.8 92.1 17.0<BR>> 10. 4.68.111.162
0.0% 39<BR>> 24.5 47.8 23.5 431.2 80.4<BR>> 11. <A href="http://te3-1-10g.ar1.pao2.gblx.net/" target=_blank>te3-1-10G.ar1.PAO2.gblx.net</A> 0.0% 39<BR>> 26.3 30.2 24.9 148.0 20.8<BR>> 12. 64.209.106.2 84.2% 39<BR>> 40.5 31.5 27.6 40.5 4.5<BR>> 13. ???<BR>> 14. 204.69.234.1 97.4% 39<BR>> 52.2 52.2 52.2 52.2
0.0<BR>><BR>_______________________________________________<BR>outages mailing list<BR><A href="mailto:outages@outages.org" ymailto="mailto:outages@outages.org">outages@outages.org</A><BR><A href="https://puck.nether.net/mailman/listinfo/outages" target=_blank>https://puck.nether.net/mailman/listinfo/outages</A><BR></DIV></DIV><!-- cg20.c4.mail.gq1.yahoo.com compressed/chunked Mon Dec 21 11:20:45 PST 2009 --></div><br>
</body></html>