
Update -- there's a routing loop between our upstream provider and Sprint. Hence the lack of DNS resolution. =) nagios:/home/fbulk# tcptraceroute 66.135.207.137 Selected device eth0.3, address 96.31.0.5, port 39237 for outgoing packets Tracing the path to 66.135.207.137 on TCP port 80 (www), 30 hops max ... 4 ins-db1-te-13-2-219.desm.netins.net (167.142.60.157) 7.058 ms 7.077 ms 6.990 ms 5 ins-dc1-et-8-2.desm.netins.net (167.142.67.5) 6.924 ms 6.993 ms 6.901 ms 6 ins-kc2-et-8-1.kmrr.netins.net (167.142.67.30) 6.917 ms 6.866 ms 6.875 ms 7 ins-kc1-et-9-1.kmrr.netins.net (167.142.67.42) 6.933 ms 6.962 ms 6.912 ms 8 144.223.35.225 15.118 ms 15.038 ms 15.105 ms 9 144.232.25.223 18.342 ms 18.489 ms 18.651 ms 10 * 144.232.25.220 24.455 ms 24.455 ms 11 sl-crs2-chi-0-7-3-0.sprintlink.net (144.232.19.119) 24.558 ms 24.743 ms 24.768 ms 12 144.232.25.223 27.911 ms 27.835 ms 31.434 ms 13 144.232.25.220 34.015 ms 33.832 ms 33.904 ms 14 sl-crs2-chi-0-7-3-0.sprintlink.net (144.232.19.119) 34.305 ms 34.130 ms 34.044 ms 15 144.232.25.223 37.271 ms 37.255 ms 37.176 ms 16 144.232.25.220 43.179 ms 43.329 ms 43.242 ms 17 sl-crs2-chi-0-7-3-0.sprintlink.net (144.232.19.119) 43.514 ms 43.587 ms 43.319 ms 18 144.232.25.223 46.578 ms 46.786 ms 46.814 ms 19 144.232.25.220 52.628 ms 52.710 ms 52.638 ms 20 sl-crs2-chi-0-7-3-0.sprintlink.net (144.232.19.119) 53.218 ms 52.951 ms 52.957 ms 21 144.232.25.223 55.959 ms 55.881 ms 55.976 ms 22 144.232.25.220 62.223 ms 62.040 ms 61.964 ms 23 sl-crs2-chi-0-7-3-0.sprintlink.net (144.232.19.119) 65.137 ms 62.283 ms 62.218 ms 24 144.232.25.223 65.440 ms 65.291 ms 65.405 ms 25 144.232.25.220 88.613 ms 71.442 ms 71.560 ms 26 sl-crs2-chi-0-7-3-0.sprintlink.net (144.232.19.119) 71.528 ms 108.371 ms 79.077 ms 27 144.232.25.223 75.200 ms 75.223 ms 74.923 ms 28 * 144.232.25.220 80.707 ms 81.060 ms 29 sl-crs2-chi-0-7-3-0.sprintlink.net (144.232.19.119) 104.564 ms 81.222 ms 81.126 ms 30 144.232.25.223 84.306 ms 84.223 ms 84.163 ms Destination not reached nagios:/home/fbulk# Frank -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Frank Bulk - iName.com Sent: Tuesday, January 17, 2012 2:20 PM To: outages@outages.org Subject: [outages] DNS resolution of ebay.com We've received two calls complaining about access to www.ebay.com. Further checking shows that none of our DNS servers can resolve either www.ebay.com or ebay.com. DIG returns a "timed out". Flushing our caches made no difference, and our upstream provider's DNS servers are acting the same way. Digging against 8.8.8.8 works fine, but against the 4 NS servers listed for ebay, they don't, probably because their DNS server is all ebaydns.com. nagios:/tmp# dig A ebay.com @96.31.0.5 ; <<>> DiG 9.7.3 <<>> A ebay.com @96.31.0.5 ;; global options: +cmd ;; connection timed out; no servers could be reached nagios:/tmp# dig A ebay.com @167.142.225.5 ; <<>> DiG 9.7.3 <<>> A ebay.com @167.142.225.5 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 41569 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;ebay.com. IN A ;; Query time: 4433 msec ;; SERVER: 167.142.225.5#53(167.142.225.5) ;; WHEN: Tue Jan 17 14:19:12 2012 ;; MSG SIZE rcvd: 26 nagios:/tmp# nagios:/tmp# dig NS ebay.com @8.8.8.8 ; <<>> DiG 9.7.3 <<>> NS ebay.com @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58612 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;ebay.com. IN NS ;; ANSWER SECTION: ebay.com. 63033 IN NS sjc-dns2.ebaydns.com. ebay.com. 63033 IN NS smf-dns2.ebaydns.com. ebay.com. 63033 IN NS smf-dns1.ebaydns.com. ebay.com. 63033 IN NS sjc-dns1.ebaydns.com. ;; Query time: 37 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Tue Jan 17 14:18:22 2012 ;; MSG SIZE rcvd: 126 nagios:/tmp# _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages