Issues connecting to hosted site

[Trippin]

I think I mentioned this before, and djbob asked me to do a tracert (I believe) so I did. If it was something else let me know, and I'll do it too!

But I cannot access my site, or helionet.org (except through proxy) at random times. I was hoping Stevie would solve this, but he hasn't. :-\

 

The weird thing is I can access my site through trippin.heliohost.org yet I can't access it through my parked domain trippin.uni.cc

Everyone else it seems can access through either.

 

Here is my tracert of my trippin.uni.cc domain, then google.com, then my trippin.uni.cc domain again, then my trippin.heliohost.org domain.

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Andrew>tracert trippin.uni.cc
Unable to resolve target system name trippin.uni.cc.

C:\Users\Andrew>tracert google.com

Tracing route to google.com [72.14.207.99]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  192.168.1.1
  2     1 ms     1 ms     1 ms  192.168.2.1
  3    40 ms    39 ms    40 ms  fl-71-3-192-1.dhcp.embarqhsd.net [71.3.192.1]
  4    39 ms    39 ms    39 ms  crflftmy01 [71.3.0.77]
  5    40 ms    39 ms    40 ms  host-105.embarqservices.net [74.5.253.105]
  6    43 ms    42 ms    43 ms  te-8-2.car1.Miami1.Level3.net [4.71.210.21]
  7    53 ms    52 ms    54 ms  ae-31-51.ebr1.Miami1.Level3.net [4.69.138.94]
  8    79 ms    71 ms    71 ms  ae-2.ebr1.Dallas1.Level3.net [4.69.140.133]
  9    73 ms    71 ms    72 ms  ae-81-81.csw3.Dallas1.Level3.net [4.69.136.130]
10    80 ms    72 ms    72 ms  ae-82-82.ebr2.Dallas1.Level3.net [4.69.136.145]
11   118 ms   107 ms   108 ms  ae-6.ebr3.NewYork1.Level3.net [4.69.137.122]
12   117 ms   107 ms   108 ms  ae-83-83.csw3.NewYork1.Level3.net [4.69.134.106]
13   113 ms   106 ms   154 ms  ae-3-89.edge1.NewYork1.Level3.net [4.68.16.142]
14   106 ms   107 ms   106 ms  GOOGLE-INC.edge1.NewYork1.Level3.net [4.71.172.86]
15   126 ms   127 ms   126 ms  216.239.43.146
16   126 ms   126 ms   126 ms  66.249.94.90
17   128 ms   140 ms   129 ms  72.14.236.130
18   127 ms   127 ms   127 ms  eh-in-f99.google.com [72.14.207.99]

Trace complete.

C:\Users\Andrew>tracert trippin.uni.cc
Unable to resolve target system name trippin.uni.cc.

C:\Users\Andrew>tracert trippin.heliohost.org

Tracing route to trippin.heliohost.org [65.19.143.3]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2     1 ms     1 ms     1 ms  192.168.2.1
  3    39 ms    39 ms    39 ms  fl-71-3-192-1.dhcp.embarqhsd.net [71.3.192.1]
  4    40 ms    39 ms    39 ms  crflftmy01 [71.3.0.77]
  5    40 ms    40 ms    39 ms  host-105.embarqservices.net [74.5.253.105]
  6    43 ms    42 ms    43 ms  te-8-2.car1.Miami1.Level3.net [4.71.210.21]
  7    43 ms    52 ms    53 ms  ae-31-51.ebr1.Miami1.Level3.net [4.69.138.94]
  8    72 ms    72 ms    72 ms  ae-2.ebr1.Dallas1.Level3.net [4.69.140.133]
  9    72 ms    72 ms    72 ms  ae-81-81.csw3.Dallas1.Level3.net [4.69.136.130]
10    72 ms    72 ms    73 ms  ae-33-89.car3.Dallas1.Level3.net [4.68.19.133]
11    72 ms    72 ms    73 ms  4.68.63.194
12   105 ms   105 ms   105 ms  las-bb1-link.telia.net [213.248.80.13]
13   135 ms   117 ms   117 ms  sjo-bb1-link.telia.net [213.248.80.18]
14   116 ms   116 ms   116 ms  hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
15   116 ms   117 ms   122 ms  10gigabitethernet1-2.core1.fmt1.he.net [66.160.158.241]
16   117 ms   117 ms   117 ms  65.19.143.3

Trace complete.

C:\Users\Andrew>

 

Then I had a friend in arkansas do a tracert for me too, and here are his results. (He's on a linux box, so I don't know if makes a difference, but the output is different than on my vista machine):

root@rebeler:/home/rebeler# tracert trippin.uni.cc
traceroute to trippin.uni.cc (65.19.143.3), 30 hops max, 40 byte packets
1  192.168.1.1 (192.168.1.1)  1.656 ms  2.917 ms *
2  * * *
3  * * *
4  * * *
5  * * *
6  * * *
7  ex2-p14-1.eqdltx.sbcglobal.net (151.164.242.42)  20.183 ms *  24.225 ms
8  * * *
9  * 10gigabitethernet1-2.core1.lax1.he.net (72.52.92.57)  58.311 ms *
10  10gigabitethernet1-3.core1.pao1.he.net (72.52.92.21)  70.270 ms * *
11  10gigabitethernet1-2.core1.fmt1.he.net (66.160.158.241)  77.360 ms *  66.850 ms
12  65.19.143.3 (65.19.143.3)  66.272 ms  66.259 ms  67.118 ms
root@rebeler:/home/rebeler# tracert google.com
traceroute to google.com (72.14.207.99), 30 hops max, 40 byte packets
1  192.168.1.1 (192.168.1.1)  1.738 ms  2.351 ms *
2  * * *
3  * * *
4  * * *
5  * * *
6  * ex1-p0-0.eqchil.sbcglobal.net (151.164.42.147)  25.537 ms *
7  * * *
8  * * *
9  * * *
10  * * *
11  * * 66.249.94.118 (66.249.94.118)  43.602 ms
12  eh-in-f99.google.com (72.14.207.99)  37.692 ms  38.253 ms  40.168 ms
root@rebeler:/home/rebeler#

 

I also know a friend in California that can see my site when it's been out for me in the past but he's not online, so I can't ask him for a tracert. If you need/want anything else from me, or can give me a solution, I'd love one. It's quite annoying to go and try to access your site, only to find out you (the owner) can't access it while everyone else it seems can.

 

Thanks!

[Ashoat]

Stevie's nameservers are now:

ns1.heliohost.org

ns2.heliohost.org

 

Point your domain to those and see if it works.

[Trippin]

Well it has been working fine, it will just randomly go out one evening, and will come back when I get up the next morning. But I have changed my name servers, so we will see what happens. Hope this fixes it!

 

----edit----

I just thought of something, I doubt this will fix it because helionet.org will not work for me either when my site is down. And it's not like I can change the name servers for helionet.org

 

 

[Ashoat]

The old nameservers were still working because they were pointing to the old server, which is configured in a DNS cluster with Stevie and so they are able to interoperate. However, when you point to the old nameservers it's still the old server that is processing your request, so that might be why you are seeing no difference.

 

About HelioNet being down: I haven't switched it to the new nameservers yet.

[Trippin]

*Keeps fingers crossed*

 

Either way though, being that that is the only problem I have with you guys, it really makes you the best free host. Period. Thanks alot and here's to hoping it works!