Last updated: Thursday, August 28, 2008 11:13 AM
In the wee small hours of the morning on August 28, my ISP (canisius.edu) persuaded the company that sells services to the company that sells services to canisius.edu to reboot the router on which canisius.edu depends.
I can now connect to moleski.net as I have in the past.
I still think there is something squirrely about IPower's setup, but that's their problem now, not mine. I'm going to declare victory and go fight other battles.
Registrant:
Martin X. Moleski, SJ
2001 Main Street
Buffalo, Martin X. Moleski, S 14208
USA
Registrar: DOTREGISTRAR
Domain Name: MOLESKI.NET
Created on: 02-NOV-02
Expires on: 02-NOV-10
Last Updated on: 10-APR-08
Administrative, Technical Contact:
X. Moleski, SJ, Martin moleski@canisius.edu
2001 Main Street
Buffalo, Martin X. Moleski, S 14208
USA
+1.7168882383
Domain servers in listed order:
NS1.IPOWER.COM
NS2.IPOWER.COM
End of Whois Information
I have owned and run http://moleski.net all by myself since 2002. If you take time to browse the site, you will see that there are many pages on it. I have two Joomla development sites there along with an installation of Dokuwiki. The files didn't get on the site by accident. I put them there. I know how the system is supposed to work. The site is not much good to me if I can't use the wiki, log into joomla, or update it with Dreamweaver, Filezilla, and UltraEdit32 (my favorite FTP clients). I seem to remember a PHP/MySQL driven photo album on the site as well.
My other sites which I edit and manage routinely, without any difficulty like I'm having with IPower:
Problem: I cannot access http://moleski.net either via browsers (Firefox, IE) or FTP clients. The site times out.
I first noticed the problem on Friday, August 15. I made several attempts to reach the site over the next couple of days. I was able to upload a number of new files using Dreamweaver around Mon Aug 18 01:04:48 2008 (timestamp on tighar.html). Later that day, I was unable to update the files with Dreamweaver (same username and password that had worked earlier in the day; I finally used File Manager in the Control Panel to update the TIGHAR files Mon Aug 18 23:59:01).
08/18/2008 3:20 PM EDT IPOWER contacted Martin Moleski (Resolved) Comment:Thank you for contacting technical support.if it was an issue with the server - you would not be able to see your site through megaproxy. it may not be your computer but something somewhere is not able to reach your server. try doing a trace route and see if where you are sitting can reach our server in bostonIf you have any other issues or concerns please feel free to reply to this email.Jeff LTier two technician
Traceroutes from independent computers not located at canisius.edu suggest that there is a systemic problem at EIG.
You can duplicate each of the five tests below by clicking on the link. You will see that they are computers run by people who have nothing to do with me or my computer or with canisius.edu. You don't have to take my word for this. You can tell that just by READING the traceroutes. Here is the description of the IP addresses that belong to canisius.edu:
OrgName: Canisius College OrgID: CANISI Address: Information Technology Services Address: 2001 Main Street City: Buffalo StateProv: NY PostalCode: 14208 Country: USNetRange: 138.92.0.0 - 138.92.255.255 CIDR: 138.92.0.0/16 NetName: CANISIUS NetHandle: NET-138-92-0-0-1 Parent: NET-138-0-0-0-0 NetType: Direct Assignment NameServer: NS3.BROADWING.NET NameServer: NS4.BROADWING.NET Comment: RegDate: 1990-04-19 Updated: 2006-06-19
If you don't see an IP address in the traceroute that begins with 138.92, then there is no Canisius machine involved in the route. That, in turn, means that the problems with the traceroute have nothing to do with the setup at Canisius.
I have the feeling that I could multiply traceroutes all day from different computer sites and never finish. Five is enough for now.
Using http://network-tools.com/
66.96.130.43 is from United States(US) in region North America
TraceRoute to 66.96.130.43 [moleski.net]
Hop (ms) (ms) (ms) IP Address Host name
1 23 26 20 72.249.0.65 -
2 33 50 29 8.9.232.73 te-3-4.car1.dallas1.level3.net
3 22 31 19 4.68.19.68 ae-22-79.car2.dallas1.level3.net
4 8 6 8 4.68.110.14 te-7-4-72.dllstx2wch010.wcg.level3.net
5 67 111 8 64.200.249.129 -
6 13 11 16 64.200.210.66 hstntx1wcx3-pos1-0-oc192.wcg.net
7 25 48 26 64.200.186.77 hstntx1wcx2-pos6-0.wcg.net
8 42 56 48 64.200.240.78 drvlga1wcx2-pos12-0.wcg.net
9 59 55 45 64.200.210.238 hrndva1wcx3-pos14-0-oc192.wcg.net
10 47 55 52 64.200.89.121 hrndva1wcx2-pos4-0-oc192.wcg.net
11 50 43 54 64.200.210.177 nycmny2wcx2-pos1-0-oc192.wcg.net
12 65 46 41 64.200.68.158 nycmny2wcx3-pos1-0-oc192.wcg.net
13 54 53 46 64.200.249.50 bstnma1wcx011-pos9-0-oc48.wcg.net
14 50 60 73 65.77.95.181 bstnma1wcx010-pos6-0-oc48.wcg.net
15 47 47 50 65.77.95.106 bstnma1wcx010-north-atlantic-gige13-0.wcg.net
16 64 60 65 207.180.56.6 -
17 Timed out Timed out Timed out -
18 63 59 59 66.96.130.43 43.130.96.66.static.eigbox.net
Using http://www.net.princeton.edu/traceroute.html
tracing path from www.net.princeton.edu to 66.96.130.43 ...
traceroute to 66.96.130.43 (66.96.130.43), 30 hops max, 40 byte packets
1 gigagate1 (128.112.128.114) 0.501 ms 0.287 ms 0.342 ms
2 vgate1 (128.112.12.22) 0.347 ms 0.321 ms 0.345 ms
3 patriotgate (204.153.48.14) 1.590 ms 1.397 ms 1.608 ms
4 ge-5-3-0.mpr1.phl2.us.above.net (208.184.48.193) 4.978 ms 4.714 ms 4.650 ms
5 ge-4-0-0.mpr1.lga5.us.above.net (64.125.31.34) 5.212 ms 4.985 ms 5.583 ms
6 64.125.28.246 (64.125.28.246) 4.873 ms 4.918 ms 4.778 ms
7 so-5-0-0.mpr1.bos2.us.above.net (64.125.29.85) 10.905 ms 10.429 ms 10.511 ms
8 64.124.50.5.available.above.net (64.124.50.5) 16.714 ms 16.805 ms 16.506 ms
9 254.252.148.207.static.yourhostingaccount.com (207.148.252.254) 17.334 ms 19.401 ms 17.651 ms
10 41.128.96.66.static.eigbox.net (66.96.128.41) 17.018 ms 17.077 ms 16.971 ms
11 * * *
12 * * *
Using http://www.opus1.com/www/traceroute.html
traceroute to MOLESKI.NET (66.96.130.43), 30 hops max, 40 byte packets
1 Firewall (192.245.12.78) 5.859 ms 5.859 ms 5.859 ms
2 Opus-GW (207.182.35.49) 5.859 ms 6.835 ms 4.882 ms
3 Opus-Login-T3 (204.17.35.105) 4.882 ms 4.882 ms 4.882 ms
4 phv-edge-03.inet.qwest.net (65.121.93.133) 6.835 ms 7.812 ms 7.812 ms
5 phn-core-02.inet.qwest.net (205.171.12.109) 7.812 ms 7.812 ms 7.812 ms
6 lap-brdr-03.inet.qwest.net (67.14.22.74) 18.553 ms 18.553 ms 18.553 ms
7 te9-3.mpd01.lax05.atlas.cogentco.com (154.54.11.125) 19.530 ms 19.530 ms 19.530 ms
8 vl3490.ccr02.lax01.atlas.cogentco.com (154.54.6.189) 17.577 ms 18.554 ms 18.554 ms
9 te3-4.ccr02.iah01.atlas.cogentco.com (154.54.5.193) 46.872 ms 50.778 ms 50.778 ms
10 te3-3.ccr02.dfw01.atlas.cogentco.com (154.54.5.137) 47.849 ms 47.849 ms 47.849 ms
11 te7-3.ccr02.mci01.atlas.cogentco.com (154.54.2.114) 56.637 ms 57.614 ms 57.614 ms
12 te3-3.ccr02.ord01.atlas.cogentco.com (154.54.6.202) 68.355 ms 68.355 ms 68.355 ms
13 te2-1.ccr02.bos01.atlas.cogentco.com (154.54.7.170) 91.791 ms 91.791 ms 92.768 ms
14 endurance-international-group.demarc.cogentco.com (38.97.106.34) 91.791 ms 92.768 ms 92.768 ms
15 * * *
16 41.128.96.66.static.eigbox.net (66.96.128.41) 92.767 ms 92.767 ms 93.744 ms
http://www.theworldsend.net/php-trace.php?host=moleski.net&submit=Trace!
Traceroute Output:
1 phonoscope-204-2-20-017.phonoscope.com (204.2.20.17) 0.382 ms 0.294 ms 0.239 ms
2 ge-1-6.r04.hstntx01.us.bb.gin.ntt.net (128.241.5.1) 0.809 ms 0.776 ms 0.718 ms
3 xe-1-3-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.4.233) 0.834 ms 0.853 ms 0.788 ms
4 as-0.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129) 10.562 ms 10.581 ms 15.824 ms
5 equinixexchange.ir1.dallas2-tx.us.xo.net (206.223.118.85) 8.313 ms 5.858 ms 5.842 ms
6 te-3-1-0.rar3.dallas-tx.us.xo.net (65.106.1.34) 6.861 ms 7.541 ms 6.716 ms
7 ge7-0-0d0.rar1.dallas-tx.us.xo.net (65.106.1.33) 18.480 ms 9.634 ms 25.322 ms
8 p1-0-0.RAR2.Chicago-IL.us.xo.net (65.106.0.33) 31.840 ms 32.019 ms 31.908 ms
9 p6-0-0.RAR1.NYC-NY.us.xo.net (65.106.0.30) 58.962 ms 58.786 ms 58.793 ms
10 p0-0-0d0.mar1.cambridge-ma.us.xo.net (65.106.3.14) 63.536 ms 63.688 ms 65.927 ms
11 207.88.86.154.ptr.us.xo.net (207.88.86.154) 66.103 ms 65.774 ms 65.764 ms
12 ip65-47-145-6.z145-47-65.customer.algx.net (65.47.145.6) 66.366 ms 66.481 ms 66.481 ms
13 * * *
14 41.128.96.66.static.eigbox.net (66.96.128.41) 72.007 ms 71.863 ms 71.712 ms
15 * * *
16 * * *
17 * *
41.128.96.66.static.eigbox.net (66.96.128.41) 69.321 ms !H
18 * * *
19 41.128.96.66.static.eigbox.net (66.96.128.41) 64.521 ms !H * *
20 *
41.128.96.66.static.eigbox.net (66.96.128.41) 69.590 ms !H *
21 * * *
22 *
41.128.96.66.static.eigbox.net (66.96.128.41) 69.571 ms !H 66.886 ms !H
done....
Results from: /usr/sbin/traceroute moleski.net:
traceroute to moleski.net (66.96.130.43), 30 hops max, 38 byte packets
1 POD-C-NH-VL4.GW.CMU.NET (128.2.4.44) 0.305 ms 0.221 ms 0.218 ms
2 CORE255-VL908.GW.CMU.NET (128.2.255.194) 0.337 ms 0.387 ms 0.370 ms
3 POD-I-CYH-VL987.GW.CMU.NET (128.2.255.250) 1.375 ms 0.425 ms 0.419 ms
4 bar-cmu-ge-4-0-0-2.3rox.net (192.88.115.185) 0.709 ms 0.599 ms 0.584 ms
5 minithan-bar-transitrail-10ge-0-1-0-0-203.3rox.net (192.88.115.26) 0.972 ms 0.801 ms 0.704 ms
6 te2-1--577.tr01-asbnva01.transitrail.net (137.164.131.193) 6.706 ms 6.667 ms 6.731 ms
7 abovenet-peer.asbnva01.transitrail.net (137.164.130.50) 6.601 ms 6.680 ms 6.727 ms
8 ge-3-0-0.mpr2.dca2.above.net (64.125.26.241) 7.644 ms 7.591 ms 7.545 ms
MPLS Label=173428 CoS=5 TTL=1 S=0
9 so-0-1-0.mpr2.lga5.us.above.net (64.125.26.106) 11.992 ms 12.002 ms 11.964 ms
MPLS Label=673141 CoS=5 TTL=1 S=0
10 so-0-0-0.cr2.lga2.us.above.net (64.125.28.254) 14.480 ms 12.074 ms 12.101 ms
MPLS Label=632372 CoS=5 TTL=1 S=0
11 so-5-0-0.mpr2.bos2.us.above.net (64.125.29.89) 17.632 ms 18.047 ms 17.610 ms
12 64.124.50.5.available.above.net (64.124.50.5) 18.460 ms 18.580 ms 18.479 ms
13 254.252.148.207.static.yourhostingaccount.com (207.148.252.254) 18.860 ms 18.756 ms 18.828 ms
14 41.128.96.66.static.eigbox.net (66.96.128.41) 19.067 ms 18.672 ms 19.034 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 41.128.96.66.static.eigbox.net (66.96.128.41) 18.798 ms !H * *
25 * 41.128.96.66.static.eigbox.net (66.96.128.41) 18.679 ms !H *
26 * 41.128.96.66.static.eigbox.net (66.96.128.41) 19.029 ms !H *
27 * 41.128.96.66.static.eigbox.net (66.96.128.41) 18.720 ms !H 19.002 ms !H
15 * * *
16 * * *
17 * * *
"This means that the target system could not be reached. More accurately, it
means that the packets could not make it there and back; they may actually be
reaching the target system but encountering problems on the return trip (more on
this later). This is possibly due to some kind of problem, but it may also be an
intentional block due to a firewall or other security measures, and the block
may affect traceroute but not actual server connections."
A trace can end with one of several error indications indicating why the trace
cannot proceed. In this example, the router is indicating that it has no route
to the target host:
4 rbrt3.exit109.com (208.225.64.50) 35.931 ms !H * 39.970 ms !H
The !H is a "host unreachable" error message (it indicates that an
ICMP error message was received). The trace will stop at this point.
Possible ICMP error messages of this nature include:
!H Host unreachable. The router has no route to the target system.
OrgName: Endurance International Group, Inc.
OrgID: EIG-12
Address: 70 Blanchard Road
City: Burlington
StateProv: MA
PostalCode: 01803
Country: US
NetRange: 66.96.128.0 - 66.96.191.255
CIDR: 66.96.128.0/18
NetName: BIZLAND-FC01
NetHandle: NET-66-96-128-0-1
Parent: NET-66-0-0-0-0
NetType: Direct Allocation
NameServer: NS1.BIZLAND.COM
NameServer: NS2.BIZLAND.COM
Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
RegDate: 2001-04-03
Updated: 2005-03-31
OrgTechHandle: KWI15-ARIN
OrgTechName: Witt, Karl
OrgTechPhone: +1-781-852-3316
OrgTechEmail: kwitt@bizland-inc.com
General Information
Hostname: 43.130.96.66.static.eigbox.net
ISP: Endurance International Group
Organization: Endurance International Group
Proxy: None detected
Type: Corporate
The Endurance International Group, Inc.
Third Floor
70 Blanchard Road
Burlington, MA 01803
U.S.A.
General Number: 866-897-5421
Telephoned 4:40 PM August 26, 2008
Service rep: John, otherwise not identifiable. He says they'll know
who he is.
John made notes on the log. John can't help me. He gave me
a number to call:
602-817-6013
He didn't tell me who I was calling. I think he said it was "tech 3."
On hold at 5:05 PM.
Marvella. Talking with some woman at 5:09 PM.
On hold at 5:13 PM. The woman needs to ask for help.
On hold again at 5:24 PM. She says if they can see it and if I can see it through a proxy server, then there is no problem. The fact that independent servers not located at canisius.edu cannot trace the route means nothing to her. It's not their problem.
IPowerWeb owns EIG?
Marvella says I may write to:
Fat lot of good that did me. We'll see if they're willing to receive the e-mail tomorrow, I guess.
********************************************** ** THIS IS A WARNING MESSAGE ONLY ** ** YOU DO NOT NEED TO RESEND YOUR MESSAGE ** ********************************************** The original message was received at Tue, 26 Aug 2008 17:56:32 -0400 (EDT) from dyna538-subnet8.canisius.edu [138.92.13.30] ----- The following addresses had transient delivery errors ----- <feedback@ipowerweb.com>
Reporting-MTA: dns; mx0.canisius.edu Arrival-Date: Tue, 26 Aug 2008 17:56:32 -0400 (EDT) Final-Recipient: rfc822; feedback@ipowerweb.com Action: delayed Status: 4.4.1 Remote-MTA: DNS; in.ipowerweb.com Last-Attempt-Date: Tue, 26 Aug 2008 22:14:10 -0400 (EDT) Will-Retry-Until: Sun, 31 Aug 2008 17:56:32 -0400 (EDT)
Subject:
Feeling very unsupported ... |
From:
"Martin X. Moleski, SJ" <moleski@canisius.edu> |
Date:
Tue, 26 Aug 2008 17:56:23 -0400 |
To:
feedback@ipowerweb.com |
John had seemed to understand the data from the traceroutes. I decided to call him back and see if he had any other suggestions about how to get some support. Connie answered the phone. She seemed not to know who John is.
Connie at EIG. She says there actually is a toll-free number I could use to call support:
1 888 511 host
1 888 511 4678
Connie put the link for this page on a support ticket. She says to wait 24 hours for results.
Chris called me back while I was downstairs for dinner. I returned his call and left a message.
to: Jeremy Nixon, veteran Usenet god cc: Mikey, Canisius ITS guru
Jeremy Nixon wrote:
>> I only noticed late in the game that I had quoted >> you on how to interpret traceroute output. It's >> a very nice page.
> Man, I can't believe that's still up. I haven't had access to that > account or its web pages in years, and yet, it remains available to > the world. :)
A very grateful world! It's on the first page for a Google of "traceroute."
>> In the traceroutes I've given, does that mean >> that 43.130.96.66.static.eigbox.net says, >> "I can't reach 66.96.130.43"? Or is it the >> computer running the traceroute that says >> this? Who sends the ICMP error message? >> eigbox.net?
> The host listed with the message is (or at least, is to the best of > our ability to detect) the one sending the reply.
OK. That [frustrates me to no end]. The eigbox is the server on which my site resides. You'd think it could find it!
> In this case, it looks like the trace errors are either due to strange > routing (probably a firewall) by deliberate configuration, or some really > bizarre network bugs.
So IPowerWeb may be doing strange routing? And is behind a firewall?
> At least at first blush. That router is sending > back replies with incorrect TTL values (resulting in the "blank" hops > and duplicated entries).
By "that router" do you mean 43.130.96.66.static.eigbox.net?
> From here, if I trace I get the host-unreachable errors. However, if I > do a trace using ICMP echo requests rather than the normal UDP method, > it works just fine. Depending on your OS, "traceroute -I" may do that > kind of trace.
No joy with XP. Using a small linux box, I can't get out of Canisius at all (I think there is something wrong with Canisius as well as with IPowerWeb):
[root@localhost ~]# traceroute -I moleski.net traceroute to moleski.net (66.96.130.43), 30 hops max, 40 byte packets 1 subnet8-gateway.canisius.edu (138.92.8.1) 0.367 ms 0.365 ms 0.383 ms 2 heimdall.canisius.edu (138.92.241.12) 1.109 ms 1.106 ms 1.070 ms
[root@localhost ~]# traceroute moleski.net -I traceroute to moleski.net (66.96.130.43), 30 hops max, 40 byte packets 1 subnet8-gateway.canisius.edu (138.92.8.1) 0.433 ms 0.416 ms 0.418 ms 2 heimdall.canisius.edu (138.92.241.12) 1.753 ms 1.757 ms 1.716 ms
I get exactly the same results with XP and tracert (doesn't have the -I switch). It doesn't get out of canisius.edu at all.
> (Works on Mac OS X.) Plus, if I do that, the route is > different at the end, which indicates that they are treating different > traffic differently. Also, I can bring up the site.
Everybody I know who has tried it outside of canisius.edu can do it; I can bring it up with megaproxy. That suggests that there is something squirrely about canisius.edu. BUT there also seems to be something squirrely about IPowerWeb's (or EIG's) setup.
> "ping" uses ICMP echo requests. Can you do "ping moleski.net"?
No joy either with XP or linux:
[root@localhost ~]# ping moleski.net PING moleski.net (66.96.130.43) 56(84) bytes of data. ^C --- moleski.net ping statistics --- 240 packets transmitted, 0 received, 100% packet loss, time 238999ms
Ping works from http://network-tools.com/default.asp?prog=ping&host=moleski.net
Ping 66.96.130.43
[moleski.net]
Round trip time to 66.96.130.43: 66 ms Round trip time to 66.96.130.43: 61 ms Round trip time to 66.96.130.43: 60 ms Round trip time to 66.96.130.43: 60 ms Round trip time to 66.96.130.43: 61 ms Round trip time to 66.96.130.43: 61 ms Round trip time to 66.96.130.43: 67 ms Round trip time to 66.96.130.43: 62 ms Round trip time to 66.96.130.43: 61 ms Round trip time to 66.96.130.43: 61 ms
Average time over 10 pings: 62 ms
Same site does a lookup OK:
IP address: 66.96.130.43 Host name: moleski.net 66.96.130.43 is from United States(US) in region North America
Another attempt at traceroute from that site fails at eigbox:
TraceRoute to 66.96.130.43 [moleski.net] Hop (ms) (ms) (ms) IP Address Host name 1 9 11 16 72.249.0.65 - 2 12 15 10 206.123.64.22 - 3 17 30 12 216.52.189.9 border4.g3-2.colo4dallas-3.ext1.dal.pnap.net 4 17 16 14 216.52.191.33 core2.tge5-1-bbnet1.ext1.dal.pnap.net 5 17 15 24 209.246.152.245 ge-6-22-117.car1.dallas1.level3.net 6 25 29 26 4.68.19.68 ae-22-79.car2.dallas1.level3.net 7 43 17 25 4.68.110.14 te-7-4-72.dllstx2wch010.wcg.level3.net 8 195 214 200 64.200.249.129 - 9 17 14 14 64.200.210.66 hstntx1wcx3-pos1-0-oc192.wcg.net 10 44 230 16 64.200.186.77 hstntx1wcx2-pos6-0.wcg.net 11 39 38 38 64.200.240.78 drvlga1wcx2-pos12-0.wcg.net 12 48 238 272 64.200.210.238 hrndva1wcx3-pos14-0-oc192.wcg.net 13 40 38 39 64.200.89.121 hrndva1wcx2-pos4-0-oc192.wcg.net 14 49 43 43 64.200.210.177 nycmny2wcx2-pos1-0-oc192.wcg.net 15 45 54 54 64.200.68.158 nycmny2wcx3-pos1-0-oc192.wcg.net 16 48 53 49 64.200.249.50 bstnma1wcx011-pos9-0-oc48.wcg.net 17 54 48 46 65.77.95.181 bstnma1wcx010-pos6-0-oc48.wcg.net 18 48 46 46 65.77.95.106 bstnma1wcx010-north-atlantic-gige13-0.wcg.net 19 78 75 80 207.180.56.6 - 20 Timed out Timed out Timed out - 21 67 60 60 66.96.130.43 43.130.96.66.static.eigbox.net
Trace complete
> Are you trying and failing only from hosts within canisius.edu?
That is my #1 problem. I don't care who else can't see the site if I can browse it (to access the wiki) and do occasional touchup with FTP (Dreamweaver, Filezilla, UltraEdit32). I'm locked out totally right now.
> It is > entirely possible that the failing traces are a red herring. It's also > possible that the target network's strange setup is interacting badly > with a router on your network (canisius.edu). I can poke at this a > little more and see if I can figure anything out.
If you find it the least bit amusing, I'd appreciate it. I need some leverage somewhere. It used to work. Now it doesn't. It might be broken on both ends.
Pasta faggiole.
Marty
Jeremy & Mikey,
Jeremy Nixon wrote:
> Are you on DSL? What operating system?
LAN. I have two computers at my desktop:
Windows XP Pro linux (Fedora Core 8)
> What I want you to try is this: reduce the MTU on your network (internet) > link to 1492. It is probably at 1500 right now. I'm not sure how you > would do that since I don't know what you're running.
I used Speedguide TCP Optimizer 2.0.3 (2006) and set it to 1492 (after a few adventures we needn't discuss here).
>> No joy with XP. Using a small linux box, I can't get >> out of Canisius at all (I think there is something >> wrong with Canisius as well as with IPowerWeb):
> Yes, your network is heavily ICMP-filtered, from the looks of it.
> What I think is happening is that someone is breaking Path MTU Discovery. > Either their network or yours is dropping ICMP Can't Fragment errors, > resulting in the packets being dropped silently.
> (The server is definitely attempting Path MTU discovery, according to > tcpdump output.)
> So, if you're on a connection with a path MTU lower than 1500 (like most > DSL), but your computer or router are sending out requests saying that > larger packets are acceptable, and someone is dropping the ICMP errors, > then that explains the timeouts.
> See if you can successfully hit this URL:
> http://moleski.net/dokuwiki/lib/tpl/doogiestpl/images/titlebackground_center.png
> That image is small enough that it will fit into one small packet, bypassing > any path-MTU issues.
Nope. No change in ping or tracert on the XP machine. I'm going to presume I'll have the same results with the linux box (I am horrendously slow at *nix stuff).
Marty (Mikey & Jeremy totally agreed that this isn't the issue in subsequent e-mails.)
Michael Szymendera wrote:
> there is nothing *wrong* with canisius. > we do a bunch of icmp filtering, and as a consequence, > traceroute won't give you the expected results.
OK. That's helpful information. Thanks.
So my inability to tracert moleski.net from canisius.edu doesn't indicate which end has the problem (IPowerWeb or Canisius).
Marty And then Mikey replied:
exactly.. I was running traceroute while logged in at the border router. [see below for more details] The ISP-side interface can see the ICMP ttl-exceeds, and I couldn't get out to the peer router at Level3.
Here is the output from my attempt to connect to moleski.net using Firefox 3. But Mikey says it doesn't mean much:
packets 2, 3, 4 show SYN attempts to your web site (the 66. address as DST) and no ack... hence, the packet dump verifies what we already know.. you can't get there :)
Hi Jeremy (and MXM],
I have a "stub" hanging off of our interner border router that I ocassionally use for testing. I connected a laptop to it earlier today, and removed the filters from our ISP interface (just to test for some wierd filtering that might be ocurring- even though we made no changes to that interface's ACLs- so if something is/was set wrong, Marty would have never been able to get off-campus to moleski.net). With my "stubby", I was not able to get to moleski.net (ping, tracreoute or http- and none of those, indeed nothing was being filtered (no ingress/egress filters at all on the ISP or "stub" interface)).
Using the "stub" off the border bypasses our PIX firewalls, packet shapers, and ACLs on the core router (all of which could have potentially mucked with Marty's access).
So, I doubt it's an MTU problem due to aggressive ICMP filtering, as I had no filters in place while testing.
We are also having trouble reaching 2 other web-sites, and the symptoms are the same. One of them has their DNS authority assigned to 4 different DNS boxes. When I "dig" those to do "A lookups", 2 work, and 2 do not. The 2 that don't are on the same /24 as the webserver that is unreachable from Canisius. The 2 DNS boxes that return data are on a different ip network entirely.
These other 2 web sites and moleski.net, incidentally, are accessible from our "test lab" (we have a Time-Warner Broadband connection that we use for testing purposes).
So, it seems to be some sort of routing issue, perhaps at our "peer" router. The ip addresses that are problematic (Marty's and the 2 other ranges) are part of our commodity connection (we have a commodity connection via Level3, and a I2 connection via NYSERNet. Both are .1q trunked to a NYSERNet POP, where they're sent off to independant peer routers. We run BGP, and get I2 routes from NYSERNet, but only a default route from Level3. Checking the route table and the ip-cef entries, all looks good. All the "unreachable networks" (Marty's and the other two) show the Level 3 peer router as the next-hop.
[I also thought it might be CEF forwarding corruption at our border, so I turned it off, flushed the cache, etc ... still didn't work]
So, I'm going to open a ticket with Level 3 tommorow, via NyserNet.
Marty always comes up with the interesting problems.
--mike
Hello Marty, Thank you for contacting us. I have once again checked by accessing your Web site and http://moleski.net/ it is working fine without any issue. I have checked the tracert result provided by you and it seems to be a temporary issue on our server. Could you please check once again from your end? If you have any further questions, please update the Support Console. Sincerely, Kris Parks Technical Specialist
Using http://network-tools.com/
TraceRoute to 66.96.130.43 [moleski.net]
| Hop | (ms) | (ms) | (ms) | IP Address | Host name |
| 1 | 24 | 12 | 8 | 72.249.0.65 | - |
| 2 | 6 | 7 | 11 | 64.129.174.181 | 64-129-174-181.static.twtelecom.net |
| 3 | 12 | 16 | 9 | 66.192.240.90 | peer-01-ge-4-0-0-0.dlfw.twtelecom.net |
| 4 | 8 | 7 | 6 | 66.28.4.173 | te9-1.mpd01.dfw01.atlas.cogentco.com |
| 5 | 8 | 6 | 7 | 154.54.7.250 | te7-1.ccr02.dfw01.atlas.cogentco.com |
| 6 | 19 | 18 | 16 | 154.54.5.170 | te3-2.ccr02.mci01.atlas.cogentco.com |
| 7 | 31 | 30 | 30 | 154.54.6.213 | te1-3.ccr02.ord01.atlas.cogentco.com |
| 8 | 62 | 61 | 62 | 154.54.6.181 | te7-2.ccr02.bos01.atlas.cogentco.com |
| 9 | 63 | 62 | 61 | 38.97.106.34 | endurance-international-group.demarc.cogentco.com |
| 10 | Timed out | Timed out | Timed out | - |
| 11 | 63 | 62 | 61 | 66.96.130.43 | 43.130.96.66.static.eigbox.net |
Trace complete
Using http://www.net.princeton.edu/traceroute.html
traceroute to 66.96.130.43 (66.96.130.43), 30 hops max, 40 byte packets 1 gigagate1 (128.112.128.114) 0.570 ms 0.305 ms 0.340 ms 2 vgate1 (128.112.12.22) 0.435 ms 1.801 ms 0.610 ms 3 patriotgate (204.153.48.14) 1.562 ms 2.065 ms 1.442 ms 4 ge-5-3-0.mpr1.phl2.us.above.net (208.184.48.193) 4.751 ms 4.802 ms 4.915 ms 5 ge-4-0-0.mpr1.lga5.us.above.net (64.125.31.34) 5.072 ms 5.758 ms 4.794 ms 6 64.125.28.246 (64.125.28.246) 5.377 ms 4.891 ms 4.882 ms 7 so-5-0-0.mpr1.bos2.us.above.net (64.125.29.85) 10.861 ms 10.569 ms 10.764 ms 8 64.124.50.5.available.above.net (64.124.50.5) 16.437 ms 16.589 ms 21.735 ms 9 254.252.148.207.static.yourhostingaccount.com (207.148.252.254) 17.469 ms 17.901 ms 17.402 ms 10 41.128.96.66.static.eigbox.net (66.96.128.41) 17.061 ms 17.342 ms 17.144 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * 41.128.96.66.static.eigbox.net (66.96.128.41) 17.124 ms !H 17.196 ms !H
Done.
Using http://www.opus1.com/www/traceroute.html
traceroute to MOLESKI.NET (66.96.130.43), 30 hops max, 40 byte packets 1 192.245.12.78 (192.245.12.78) 6.835 ms 6.835 ms 5.859 ms 2 Opus-GW (207.182.35.49) 5.859 ms 5.859 ms 4.882 ms 3 Opus-Login-T3 (204.17.35.105) 4.882 ms 4.882 ms 4.882 ms 4 phv-edge-03.inet.qwest.net (65.121.93.133) 42.966 ms 42.966 ms 42.966 ms 5 phn-core-02.inet.qwest.net (205.171.12.109) 7.812 ms 7.812 ms 7.812 ms 6 lap-brdr-03.inet.qwest.net (67.14.22.74) 48.825 ms 48.825 ms 49.802 ms 7 te9-3.mpd01.lax05.atlas.cogentco.com (154.54.11.125) 47.849 ms 47.849 ms 47.849 ms 8 vl3491.ccr02.lax01.atlas.cogentco.com (154.54.3.141) 18.554 ms 19.530 ms 19.530 ms 9 te4-1.ccr02.sjc01.atlas.cogentco.com (154.54.5.69) 29.295 ms 29.295 ms 29.295 ms 10 te2-1.ccr02.sfo01.atlas.cogentco.com (154.54.1.129) 29.295 ms 30.272 ms 30.272 ms 11 te9-3.ccr02.mci01.atlas.cogentco.com (154.54.24.118) 67.378 ms 67.378 ms 67.378 ms 12 te3-3.ccr02.ord01.atlas.cogentco.com (154.54.6.202) 65.425 ms 66.402 ms 67.378 ms 13 te2-1.ccr02.bos01.atlas.cogentco.com (154.54.7.170) 89.838 ms 89.838 ms 89.838 ms 14 endurance-international-group.demarc.cogentco.com (38.97.106.34) 90.814 ms 90.814 ms 90.814 ms 15 * * * 16 41.128.96.66.static.eigbox.net (66.96.128.41) 91.791 ms 91.791 ms 91.791 ms
http://www.theworldsend.net/php-trace.php?host=moleski.net&submit=Trace!
Traceroute Output:
1 phonoscope-204-2-20-017.phonoscope.com (204.2.20.17) 0.395 ms 0.288 ms 0.249 ms 2 ge-1-6.r04.hstntx01.us.bb.gin.ntt.net (128.241.5.1) 0.844 ms 0.786 ms 0.743 ms 3 xe-1-3-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.4.233) 0.828 ms 0.819 ms 0.794 ms 4 as-0.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129) 10.580 ms 10.591 ms 14.989 ms 5 equinixexchange.ir1.dallas2-tx.us.xo.net (206.223.118.85) 8.395 ms 6.021 ms 5.765 ms 6 te-3-1-0.rar3.dallas-tx.us.xo.net (65.106.1.34) 6.595 ms 6.773 ms 6.488 ms 7 ge7-0-0d0.rar1.dallas-tx.us.xo.net (65.106.1.33) 6.525 ms 6.550 ms 6.451 ms 8 p1-0-0.RAR2.Chicago-IL.us.xo.net (65.106.0.33) 31.852 ms 31.830 ms 31.780 ms 9 p6-0-0.RAR1.NYC-NY.us.xo.net (65.106.0.30) 58.761 ms 58.752 ms 58.804 ms 10 p0-0-0d0.mar1.cambridge-ma.us.xo.net (65.106.3.14) 63.424 ms 63.396 ms 65.935 ms 11 207.88.86.154.ptr.us.xo.net (207.88.86.154) 65.722 ms 65.576 ms 65.719 ms 12 ip65-47-145-6.z145-47-65.customer.algx.net (65.47.145.6) 66.407 ms 66.366 ms 66.456 ms 13 * * * 14 41.128.96.66.static.eigbox.net (66.96.128.41) 71.827 ms 71.793 ms 71.716 ms 15 * * * 16 * * * 17 * * * 18 * * * 19 * 41.128.96.66.static.eigbox.net (66.96.128.41) 64.479 ms !H * 20 * * 41.128.96.66.static.eigbox.net (66.96.128.41) 67.076 ms !H 21 41.128.96.66.static.eigbox.net (66.96.128.41) 64.276 ms !H * 69.466 ms !H
done....
Results from: /usr/sbin/traceroute moleski.net:
traceroute to moleski.net (66.96.130.43), 30 hops max, 38 byte packets 1 POD-C-NH-VL4.GW.CMU.NET (128.2.4.44) 0.261 ms 0.218 ms 0.203 ms 2 CORE255-VL908.GW.CMU.NET (128.2.255.194) 0.353 ms 0.307 ms 0.304 ms 3 POD-I-CYH-VL987.GW.CMU.NET (128.2.255.250) 0.473 ms 0.417 ms 0.407 ms 4 bar-cmu-ge-4-0-0-2.3rox.net (192.88.115.185) 66.808 ms 53.390 ms 1.677 ms 5 minithan-bar-transitrail-10ge-0-1-0-0-203.3rox.net (192.88.115.26) 1.336 ms 0.740 ms 0.717 ms 6 te2-1--577.tr01-asbnva01.transitrail.net (137.164.131.193) 6.701 ms 6.669 ms 6.663 ms 7 abovenet-peer.asbnva01.transitrail.net (137.164.130.50) 6.677 ms 6.595 ms 6.595 ms 8 ge-3-0-0.mpr2.dca2.above.net (64.125.26.241) 7.608 ms 7.508 ms 7.494 ms MPLS Label=213588 CoS=5 TTL=1 S=0 9 so-0-1-0.mpr2.lga5.us.above.net (64.125.26.106) 11.919 ms 12.049 ms 11.916 ms MPLS Label=727285 CoS=5 TTL=1 S=0 10 so-0-0-0.cr2.lga2.us.above.net (64.125.28.254) 12.228 ms 12.160 ms 12.090 ms MPLS Label=639108 CoS=5 TTL=1 S=0 11 so-5-0-0.mpr2.bos2.us.above.net (64.125.29.89) 17.600 ms 17.709 ms 17.563 ms 12 64.124.50.5.available.above.net (64.124.50.5) 18.608 ms 18.349 ms 18.389 ms 13 254.252.148.207.static.yourhostingaccount.com (207.148.252.254) 21.538 ms 18.769 ms 18.853 ms 14 41.128.96.66.static.eigbox.net (66.96.128.41) 18.733 ms 18.786 ms 18.806 ms 15 * * * 16 * * * 17 * * 41.128.96.66.static.eigbox.net (66.96.128.41) 18.826 ms !H 18 41.128.96.66.static.eigbox.net (66.96.128.41) 18.765 ms !H * 18.817 ms !H
Look how the time has flown! I guess I won't have to wake up to try a "quiet time" after all.
I've picked another server. San Diego Supercomputer Center.
FROM www.sdsc.edu TO moleski.net at Tue Aug 26 23:04:35 PDT 2008.
traceroute: Warning: Multiple interfaces found; using 132.249.21.59 @ bge0:1 traceroute to moleski.net (66.96.130.43), 30 hops max, 40 byte packets 1 lightning.sdsc.edu (132.249.20.6) 0.580 ms 0.362 ms 0.353 ms 2 piranha.sdsc.edu (132.249.30.8) 50.562 ms 55.396 ms 0.422 ms 3 tus-dc1--sdsc-sdsc2-ge.cenic.net (137.164.24.173) 3.095 ms 2.972 ms 3.097 ms 4 dc-tus-agg1--tus-dc1-ge.cenic.net (137.164.46.76) 3.100 ms 3.052 ms 3.099 ms 5 dc-lax-dc2--tus-dc1-pos.cenic.net (137.164.22.42) 3.851 ms 3.809 ms 3.984 ms 6 dc-lax-core2--lax-agg2-ge.cenic.net (137.164.46.113) 5.085 ms 4.545 ms 4.220 ms 7 dc-lax-peer1--lax-core2-ge.cenic.net (137.164.46.118) 4.097 ms 3.926 ms 3.985 ms 8 xo--lax-px1-ge.cenic.net (198.32.251.46) 4.321 ms 4.286 ms 4.105 ms 9 te-3-1-0.rar3.la-ca.us.xo.net (65.106.1.54) 4.333 ms 4.308 ms 4.348 ms 10 ge7-0-0d0.rar1.la-ca.us.xo.net (65.106.1.53) 4.853 ms 6.448 ms 4.784 ms 11 p0-0-0d0.rar2.la-ca.us.xo.net (65.106.1.50) 35.584 ms 17.255 ms 23.968 ms 12 p6-0-0.rar1.dallas-tx.us.xo.net (65.106.0.13) 37.841 ms 37.636 ms 37.640 ms 13 p1-0-0.RAR2.Chicago-IL.us.xo.net (65.106.0.33) 64.137 ms 64.050 ms 64.124 ms 14 p6-0-0.RAR1.NYC-NY.us.xo.net (65.106.0.30) 93.833 ms 93.910 ms 93.826 ms 15 p0-0-0d0.mar1.cambridge-ma.us.xo.net (65.106.3.14) 98.573 ms 98.520 ms 98.450 ms 16 207.88.86.154.ptr.us.xo.net (207.88.86.154) 98.277 ms 98.346 ms 98.312 ms 17 ip65-47-145-6.z145-47-65.customer.algx.net (65.47.145.6) 105.902 ms 105.961 ms 105.806 ms 18 250.252.148.207.static.yourhostingaccount.com (207.148.252.250) 106.314 ms 106.267 ms 106.359 ms 19 41.128.96.66.static.eigbox.net (66.96.128.41) 106.315 ms 106.295 ms 106.190 ms 20 * * * 21 * * * 22 * * * 23 * * * 24 41.128.96.66.static.eigbox.net (66.96.128.41) 106.261 ms !H * * 25 41.128.96.66.static.eigbox.net (66.96.128.41) 106.432 ms !H 106.430 ms !H *
Dear Kris,
I am happy to repeat the experiment.
Is midnight on the East Coast a quiet enough time? Shall I get up a few hours from now and try again?
Here are the repeated results from the five tests, confirming the problem at your end:
http://www3.canisius.edu/~moleski/tmp/eig.html#miracle
You may notice that I have no trouble communicating with www.ipower.com. Nor with any of the other three websites for which I am webmaster. I wonder whether the difference could possibly be accounted for by a different setup at your end?
Looking forward to hearing from you with more suggestions about things to test.
I can log into ipower.com for customer support. I have been doing that for nine days now since I filed the first support ticket on August 18.
I wonder whether ipower.com can be traced?
Using http://www.net.princeton.edu/traceroute.html
tracing path from www.net.princeton.edu to 64.150.175.20 ...
traceroute to 64.150.175.20 (64.150.175.20), 30 hops max, 40 byte packets
1 gigagate1 (128.112.128.114) 0.606 ms 0.308 ms 0.333 ms
2 vgate1 (128.112.12.22) 0.372 ms 0.316 ms 0.351 ms
3 gi-6-0-226.hse1.phlapa02.paetec.net (209.92.27.33) 2.038 ms 1.988 ms 1.914 ms
4 ge-1-1-0-311.core02.phlapa02.paetec.net (169.130.105.19) 2.482 ms 2.371 ms 2.453 ms
5 so-0-2-0.core01.asbnva01.paetec.net (169.130.80.237) 6.158 ms 6.018 ms 5.843 ms
6 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 8.625 ms 9.542 ms 8.416 ms
7 vl3495.mpd01.dca02.atlas.cogentco.com (154.54.5.61) 8.673 ms vl3497.mpd01.dca02.atlas.cogentco.com (154.54.5.65) 8.965 ms vl3494.mpd01.dca02.atlas.cogentco.com (154.54.5.41) 8.562 ms
8 te8-4.ccr02.dca01.atlas.cogentco.com (154.54.6.25) 65.173 ms te2-4.ccr02.dca01.atlas.cogentco.com (154.54.7.1) 173.599 ms vl3493.ccr02.dca01.atlas.cogentco.com (154.54.7.229) 160.347 ms
9 te3-4.ccr02.bos01.atlas.cogentco.com (154.54.6.137) 21.519 ms 20.550 ms 20.336 ms
10 gi0-2.na21.b006523-1.bos01.atlas.cogentco.com (66.28.5.214) 21.567 ms 21.383 ms 21.455 ms
11 endurance-international-group.demarc.cogentco.com (38.99.213.62) 21.415 ms 21.467 ms 21.089 ms
12 36.225.148.207.static.yourhostingaccount.com (207.148.225.36) 21.577 ms 21.994 ms 21.997 ms
13 64.150.175.20 (64.150.175.20) 21.647 ms 30.385 ms 22.162 ms
Done.
That's what a successful trace looks like.
That's what a correctly configured server looks like.
I wonder whether there is some difference in setup?
So while I'm working on this report, neatening it up and hoping that someone at IPower will actually read it and think about it, along comes an e-mail reporting a dead link on moleski.net. I sure wish I could fix it.
-------- Original Message --------
Subject: Big 8 Newsgroup moderation / a little status update
Date: Wed, 27 Aug 2008 00:42:33 -0400
From: {name withheld to protect the innocent}
To: <moleski@canisius.edu>
Hello Martin X. Moleski, SJ,
You may not remember me, but you helped us out quite a bit when we were setting up the moderated newsgroup misc.writing.screenplays.moderated. I happened to glance in at news.groups, which I haven't done in about 2 years, and got all nostalgic about the whole process we went through and how much you, Ru and Russ helped us, and so I hunted around the interweb and found moleski.net, and found that you actually have a few references to our little teapot-tempest, so I thought I'd let you know how the newsgroup has turned out.
Pretty well, thanks.
MWSM is about two-and-a-half years old now, and we've managed to muddle along using just our robo-moderator without having to intervene with any human moderation, except that I clean out the spam filter about once every three or four months, as some nasty little green 11-legged creatures keep clogging it up. Sort of internet Zebra Mussels.
All the professional writers and all the regular non-writers moved over to MWSM, leaving MWS as a barren wasteland populated by a couple of cross-posters and trolls. MWS had 106 posts this past month and MWSM had 2340. The moderated group is still about 75% off-topic, but it's generally good-spirited, and has managed to attract new writers -- a fellow who writes radio drama for the BBC found us, has have several winners of major screenwriting contests and a few more established writers. When serious on-topic discussion happens, the forum allows it to go on and on without the old, lame cross-posting troll hoisting threads for his own purposes.
The group is healthy, and all thanks to a bit of light moderation and to the folks who supported our efforts to go in this direction.
I noticed that you have links on your site to the moderated screenwriting FAQ, which has moved. So if you're interested in keeping your links up-to-date, the FAQ is now here:
The MWSM FAQ: http://www.panix.com/~mwsm/faq.html
We also have a supplementary FAQ, which is a single post to MWSM from one of
our more successful and prolific screenwriters, Neal Marshall Stevens, which
I put up as it's own standalone FAQ for beginners. That one's here:
http://www.panix.com/~mwsm/nms_faq.html
Anyway, I really enjoyed my peek into your website tonight. You're into all
sorts of interesting things, and it's personal sites like this that make the
web the fun, interesting and informative place that it is. My own site
(just in the service of full disclosure, rather than because it's terribly
interesting) is here: {...} It's always a mess
because it's a sort of sandbox that I use to demonstrate blogging software
and other stuff to my classes at {...}. At the moment,
because I needed to demonstrate some audio editing techniques, there are
songs my daughter sang for me, highlighted in the middle, along with some
class notes from last semester.
I hope you're well and happy,
{signed by the fan of my website and my work in Usenet}
I don't have to wait for the folks at IPower to check the error logs. I can access them myself! I can get into the control panel! Maybe there will be a clue there! What a great idea! I got out of bed, turned the computer back on, logged into IPower.com ...
... and got skunked again. And again. You didn't think I would try just one file, did you? I tried 20080826 next. Four times. Same error message. So here I am, contacting the server administrators.
The source URL for the file transfer was http://moleskin.ipower.com/stats/access_log_20080827.gz
I'll bet I can repeat this miracle, too! But not tonight. I've got to get SOME sleep before class tomorrow.
What I can do via Control Panel |
What I cannot do via Control Panel |
File manager:
|
File manager:
|
Stats:
|
|
| View My Site (http://moleskin.ipower.com/) | |
I got partial copies of the two most recent access logs. They only show successful access. He gave me a line from the CGI error log, but it wasn't relevant to the problem. But he did do what I asked him to do, and pretty promptly. I'm grateful for that.
|
||||
|
||||
http://www.analogx.com/contents/dnsdig.htm
No problems found!
http://www.squish.net/dnscheck/ -- asking for CNAME; one error reported; dozens of other paths had no problem
Referral A.GTLD-SERVERS.net |
Asking A.GTLD-SERVERS.net (192.5.6.30) for moleski.net (type CNAME) |
|
Referral ns1.ipower.com |
Asking ns1.ipower.com (66.96.142.109) for moleski.net (type CNAME) |
|
| Response is: |
|
Referral ns2.ipower.com |
Asking ns2.ipower.com (65.254.254.144) for moleski.net (type CNAME) |
|
| Response is: |
|
| Response is: |
Checking name server--no authoritative results.
Referral A.GTLD-SERVERS.net |
Asking A.GTLD-SERVERS.net (192.5.6.30) for moleski.net (type NS) |
|
| Response is: |
|
Referral B.GTLD-SERVERS.net |
Asking B.GTLD-SERVERS.net (192.33.14.30) for moleski.net (type NS) |
|
| Response is: |
|
Referral C.GTLD-SERVERS.net |
Asking C.GTLD-SERVERS.net (192.26.92.30) for moleski.net (type NS) |
|
| Response is: |
|
Referral D.GTLD-SERVERS.net |
Asking D.GTLD-SERVERS.net (192.31.80.30) for moleski.net (type NS) |
|
| Response is: |
|
Referral E.GTLD-SERVERS.net |
Asking E.GTLD-SERVERS.net (192.12.94.30) for moleski.net (type NS) |
|
| Response is: |
|
Referral F.GTLD-SERVERS.net |
Asking F.GTLD-SERVERS.net (192.35.51.30) for moleski.net (type NS) |
|
| Response is: |
|
Referral G.GTLD-SERVERS.net |
Asking G.GTLD-SERVERS.net (192.42.93.30) for moleski.net (type NS) |
|
| Response is: |
|
Referral H.GTLD-SERVERS.net |
Asking H.GTLD-SERVERS.net (192.54.112.30) for moleski.net (type NS) |
|
| Response is: |
|
Referral I.GTLD-SERVERS.net |
Asking I.GTLD-SERVERS.net (192.43.172.30) for moleski.net (type NS) |
|
| Response is: |
|
Referral J.GTLD-SERVERS.net |
Asking J.GTLD-SERVERS.net (192.48.79.30) for moleski.net (type NS) |
|
| Response is: |
|
Referral K.GTLD-SERVERS.net |
Asking K.GTLD-SERVERS.net (192.52.178.30) for moleski.net (type NS) |
|
| Response is: |
|
Referral L.GTLD-SERVERS.net |
Asking L.GTLD-SERVERS.net (192.41.162.30) for moleski.net (type NS) |
|
| Response is: |
|
Referral M.GTLD-SERVERS.net |
Asking M.GTLD-SERVERS.net (192.55.83.30) for moleski.net (type NS) |
|
| Response is: |
|
| Response is: |
There is no PTR record for moleski.net (not relevant to the problem; just noticing).
whois ipower.com:
Registrar of Record: TUCOWS, INC.
Record last updated on 25-Aug-2008.
Record expires on 13-Jul-2016.
Record created on 14-Jul-1997.
Registrar Domain Name Help Center:
http://domainhelp.tucows.com
Domain servers in listed order:
NS1.IPOWERDNS.COM
NS1.IPOWER.COM 66.96.142.109
NS2.IPOWERWEB.NET
NS2.IPOWERDNS.COM
NS2.IPOWER.COM 65.254.254.144
NS1.IPOWERWEB.NET
But Zonecheck says:
Unable to find nameserver IP address(es) for ns1.ipowerdns.com.
Profile: N/A
Statistics: 0 tests in 0.00 sec accross 0 nameservers
Release: ZoneCheck-2.0.4
Last generated: 2008/08/28 05:32 UTC
dig can find it:
... here is the dig result for 'ipower.com' from server 'NS1.IPOWERDNS.COM' [dig @'NS1.IPOWERDNS.COM' 'ipower.com' 'A']
; <<>> DiG 9.3.2 <<>> @NS1.IPOWERDNS.COM ipower.com A |
"You are coming from IP address 138.92.13.30 using port 3417.
A DNS reverse lookup on this IP address does not work."
BGP4.net wiki -- lots more traceroute sites to pick from.
Megaproxy -- shows that moleski.net is accessible to some folks.
