More details:
From an outside host: $ dig MX mchsi.com @74.84.103.134
; <<>> DiG 9.9.2-vjs287.12 <<>> MX mchsi.com @74.84.103.134 ;; global options: +cmd ;; connection timed out; no servers could be reached $
From my main host: # tcptraceroute 74.84.103.134 53 Selected device eth0.3, address 96.31.0.5, port 52176 for outgoing packets Tracing the path to 74.84.103.134 on TCP port 53 (domain), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.234 ms 0.180 ms 0.192 ms 2 sxct.sxcy.mtcnet.net (167.142.156.197) 0.210 ms 0.124 ms 0.119 ms 3 premier.sxcy-mlx.fbnt.netins.net (173.215.60.5) 1.639 ms 1.639 ms 1.605 ms 4 ins-db1-te-13-2-219.desm.netins.net (167.142.60.157) 7.835 ms 7.791 ms 7.789 ms 5 ins-dc1-et-8-2.desm.netins.net (167.142.67.5) 7.958 ms 7.812 ms 7.839 ms 6 te-3-3.car2.KansasCity1.Level3.net (4.53.34.113) 109.795 ms 114.215 ms 13.990 ms 7 ae-11-11.car1.KansasCity1.Level3.net (4.69.135.233) 51.092 ms 23.691 ms 35.036 ms 8 ae-5-5.ebr2.Dallas1.Level3.net (4.69.135.230) 23.147 ms 23.163 ms 23.091 ms 9 ae-82-82.csw3.Dallas1.Level3.net (4.69.151.153) 23.102 ms 23.145 ms 23.195 ms 10 ae-3-80.edge10.Dallas1.Level3.net (4.69.145.146) 23.158 ms 23.130 ms 23.110 ms 11 ATT (4.68.62.230) 26.091 ms 27.334 ms 27.873 ms 12 cr1.dlstx.ip.att.net (12.123.16.86) 38.178 ms 38.530 ms 35.526 ms 13 cr2.kc9mo.ip.att.net (12.122.28.86) 34.162 ms 38.143 ms 34.972 ms 14 12.122.150.205 79.134 ms 65.759 ms 49.982 ms 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Destination not reached #
-----Original Message----- From: Frank Bulk [mailto:frnkblk@iname.com] Sent: Thursday, January 31, 2013 5:39 PM To: outages@outages.org Subject: Mediacom DNS server issue? I was first alerted by our email server because there was no DNS resolution for mchsi.com. Every indication from my testing is that Mediacom's two DNS servers: NS1.MCOMDC.COM 74.84.103.134 NS2.MCOMDC.COM 74.84.119.134 are down. I can't query anything about mchsi.com or mediacomcable.com, but www.mediacomcc.com, which uses different nameservers, resolved just fine. Frank