Print

Print


I found an old A record for digitalplains.net from DNShistory.org -- looks like a routing loop on Knology's network:

nagios:/home/fbulk# tcptraceroute 216.16.38.67
Selected device eth0.3, address 96.31.0.5, port 37082 for outgoing packets
Tracing the path to 216.16.38.67 on TCP port 80 (www), 30 hops max
 1  router-core-inside.mtcnet.net (96.31.0.254)  0.260 ms  0.179 ms  0.294 ms
 2  sxct.movl.mtcnet.net (167.142.156.194)  0.201 ms  0.126 ms  0.133 ms
 3  premier.movl-mlx.fbnt.netins.net (173.215.60.1)  2.005 ms  1.956 ms  1.936 ms
 4  ins-kb1-te-13-2-220.kmrr.netins.net (167.142.64.253)  6.404 ms  6.402 ms  6.422 ms
 5  ins-kc2-et-8-3.kmrr.netins.net (167.142.67.37)  8.122 ms  8.060 ms  8.047 ms
 6  ins-dc1-et-8-1.desm.netins.net (167.142.67.29)  8.120 ms  8.091 ms  8.124 ms
 7  te-3-3.car2.KansasCity1.Level3.net (4.53.34.113)  14.952 ms  41.355 ms  14.533 ms
 8  ae-4-4.ebr2.Denver1.Level3.net (4.69.135.238)  35.185 ms  30.963 ms  26.955 ms
 9  ae-3-3.ebr1.Chicago2.Level3.net (4.69.132.62)  51.294 ms  51.304 ms  51.312 ms
10  ae-1-51.edge4.Chicago3.Level3.net (4.69.138.134)  51.721 ms  51.737 ms  51.760 ms
11  KNOLOGY-INC.edge4.Chicago3.Level3.net (4.53.98.42)  51.487 ms  51.502 ms  51.497 ms
12  cr01.xe-1-2-0.siouxfalls.hubh.knology.net (24.214.2.6)  67.504 ms  89.639 ms  67.464 ms
13  user-24-96-198-142.knology.net (24.96.198.142)  67.610 ms  67.558 ms  67.570 ms
14  user-24-96-198-141.knology.net (24.96.198.141)  67.865 ms  67.828 ms  67.848 ms
15  user-24-96-198-142.knology.net (24.96.198.142)  67.572 ms  67.583 ms  67.611 ms
16  user-24-96-198-141.knology.net (24.96.198.141)  96.295 ms  67.852 ms  67.811 ms
17  user-24-96-198-142.knology.net (24.96.198.142)  67.694 ms  67.605 ms  67.602 ms
18  user-24-96-198-141.knology.net (24.96.198.141)  67.879 ms  67.861 ms  67.810 ms
19  user-24-96-198-142.knology.net (24.96.198.142)  67.613 ms  67.592 ms  67.660 ms
20  user-24-96-198-141.knology.net (24.96.198.141)  67.833 ms  85.509 ms  67.876 ms
21  user-24-96-198-142.knology.net (24.96.198.142)  67.620 ms  67.637 ms  67.659 ms
22  user-24-96-198-141.knology.net (24.96.198.141)  67.836 ms  67.863 ms  67.928 ms
23  user-24-96-198-142.knology.net (24.96.198.142)  67.672 ms  67.648 ms  67.682 ms
24  user-24-96-198-141.knology.net (24.96.198.141)  67.940 ms  67.955 ms  118.981 ms
25  user-24-96-198-142.knology.net (24.96.198.142)  67.727 ms  67.797 ms  67.707 ms
26  user-24-96-198-141.knology.net (24.96.198.141)  67.903 ms  67.908 ms  67.956 ms
27  user-24-96-198-142.knology.net (24.96.198.142)  67.719 ms  67.715 ms  67.736 ms
28  user-24-96-198-141.knology.net (24.96.198.141)  68.070 ms  67.926 ms  67.972 ms
29  user-24-96-198-142.knology.net (24.96.198.142)  67.835 ms  67.724 ms^C

Frank

-----Original Message-----
From: MICE Discuss [mailto:[log in to unmask]] On Behalf Of Frank Bulk
Sent: Thursday, August 23, 2012 2:38 PM
To: [log in to unmask]
Subject: [MICE-DISCUSS] MNNS or Digital Plains outage?

We have some email queued up to a domain that use digitalplains.net DNS servers (company based in Slayton).  Those servers don't respond, and calling the target domain (based in Pipestone) they said that there's an issue upstream, something with Knology.  Apparently Digital Plains recently assumed responsibility for all MNNS.COM services, and I can't hit any of their web properties, either.  I called Digital Plains toll free support number, but it just goes to someone's voicemail.

Anyone know what's going on?

Frank

########################################################################

To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

########################################################################

To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1