1
svaha
Can't get to my site.
  • 2007/2/25 10:45

  • svaha

  • Just can't stay away

  • Posts: 896

  • Since: 2003/8/2 2


Hi, I don't even know if this is XOOPS related.
I'm building a portal site on http://www.amevita.eu
After I switched from shared ip to dedicated ip I can't get on my site anymore.

The only way to get on my site is when I do it through a proxy server like hidemyass.com

Others have no problem getting to my site.

I tried several things, switch off firewall, switched of virusscanner, tried on different computers, cleared cache of browsers, cleared dns cache (ipconfig /flusdns), put my site in the 'hosts' file of the computer, but no result.
When I use tracert I get to my host but then it's only timeout.

I have no ip blocking set on my XOOPS (2.016) and protector not yet installed.

Has anyone ever encountered this wierd problem?

2
MadFish
Re: Can't get to my site.
  • 2007/2/25 11:10

  • MadFish

  • Friend of XOOPS

  • Posts: 1056

  • Since: 2003/9/27


Can you access your site by typing in the IP number in your browser? (ie. is the problem just with accessing your site via the domain name, or does it affect the IP as well?)

One possibility is that the DNS your computer is pointing at is not working properly. Suggest you point your connection at a different DNS and see if it works.

Another possibility is that your own ISP is blocking your site, maybe on purpose or maybe unintentionally. This happens all the time, at least in Thailand! If you don't have any luck with the above, give them a call and see if they can help.

3
svaha
Re: Can't get to my site.
  • 2007/2/25 12:52

  • svaha

  • Just can't stay away

  • Posts: 896

  • Since: 2003/8/2 2


When I use the dedicated IP number, it's the same result.

The connection between IP and name is correct, that I can see with nslookup.

I've opened a ticket for this problem two days ago (servage.net is my host), and they can't find anything on their side.

My isp is dutch (versatel), do you think they could block me for just this site? Because otherwise I've no problem accessing sites on the internet.

When I 'do' a tracert from my home to amevita.eu, I get this result.


Quote:

Bezig met het traceren van de route naar amevita.eu [77.232.70.123]

via maximaal 30 hops:



1 <1 ms <1 ms <1 ms 192.168.1.254

2 7 ms 7 ms 7 ms 195.190.249.80

3 12 ms 12 ms 12 ms unlabelled.versatel.net [62.58.150.9]

4 13 ms 13 ms 13 ms 212.53.18.3

5 13 ms 13 ms 13 ms te-1-4.car1.Amsterdam1.Level3.net [212.72.46.49]

6 13 ms 13 ms 17 ms ae-31-51.ebr1.Amsterdam1.Level3.net [4.68.120.30]

7 24 ms 17 ms 18 ms ae-2.ebr2.Dusseldorf1.Level3.net [4.69.133.90]

8 17 ms 17 ms 18 ms ae-1-100.ebr1.Dusseldorf1.Level3.net [4.69.132.129]

9 20 ms 32 ms 20 ms ae-2.ebr2.Frankfurt1.Level3.net [4.69.132.138]

10 20 ms 36 ms 20 ms ae-22-52.car2.Frankfurt1.Level3.net [4.68.118.48]

11 20 ms 20 ms 20 ms 62.67.38.214

12 20 ms 20 ms 20 ms fra20isp6.versatel.de [62.214.110.66]

13 25 ms 25 ms 55 ms 62.214.110.145

14 59 ms 28 ms 26 ms te-07-01.dor002isp005.versatel.de [62.214.110.133]

15 26 ms 26 ms 27 ms hhb2isp5.versatel.de [62.214.110.109]

16 30 ms 30 ms 35 ms vthh-rvt-ge.hhde.ip.servage.net [62.214.89.134]

17 30 ms 30 ms 30 ms cs1-1000M.flde.ip.servage.net [77.232.64.10]

18 * * * Time-out bij opdracht.

19 * * * Time-out bij opdracht.

20 * * * Time-out bij opdracht.

4
skenow
Re: Can't get to my site.
  • 2007/2/25 14:48

  • skenow

  • Home away from home

  • Posts: 993

  • Since: 2004/11/17


Based on your tracert, your request is going to your host (servage) and is not completing. And since you are successful when using a proxy, I would bet that your host has your home IP in a blocked range for some reason. They should be able to resolve this for you.

5
svaha
Re: Can't get to my site.
  • 2007/2/27 14:28

  • svaha

  • Just can't stay away

  • Posts: 896

  • Since: 2003/8/2 2


Thanks for your answers.

I tried some more things, for instance choose the nameservers of opendns.com to be the nameservers for windows and my router, but no succes.

My isp has no ban on my own ip number, bu the cause is probably the caching of the nameservers of servage.
It could take up to one week before this cache is refreshed.
So I will wait a few days more to be absolute sure.

6
seventhseal
Re: Can't get to my site.

Here's a traceroute from where I was this morning :

Quote:

traceroute to amevita.eu (82.140.42.33), 30 hops max, 40 byte packets
1 65.23.58.129.nw.nuvox.net (65.23.58.129) 2.083 ms 1.990 ms 3.057 ms
2 se2-0-18c1.kscyks-na-ca001.nw.nuvox.net (65.23.56.185) 6.084 ms 5.011 ms 5.234 ms
3 207-67-11-89.static.twtelecom.net (207.67.11.89) 100.003 ms 100.764 ms 108.050 ms
4 207-67-11-89.static.twtelecom.net (207.67.11.89) 115.066 ms 112.854 ms 109.354 ms
5 core-02-ge-0-1-0-538.chrl.twtelecom.net (66.192.242.240) 123.797 ms 120.697 ms 118.197 ms
6 core-01-so-0-0-0-0.asbn.twtelecom.net (66.192.255.19) 114.993 ms 114.448 ms 111.090 ms
7 peer-01-ge-0-0-0-1.asbn.twtelecom.net (64.129.249.10) 118.795 ms 116.744 ms 112.952 ms
8 * * *
9 pos-6-0.dor002ip005.versatel.de (213.30.194.234) 164.315 ms 162.727 ms 167.491 ms
10 ge-05-01-504.dor002isp005.versatel.de (62.214.110.102) 162.662 ms 156.239 ms 157.472 ms
11 62.214.110.121 (62.214.110.121) 161.707 ms 158.805 ms 155.508 ms
12 vthh-rvt-ge.hhde.ip.servage.net (62.214.89.134) 157.150 ms 157.504 ms 163.458 ms
13 cs1-1000M.flde.ip.servage.net (77.232.64.10) 160.081 ms 157.829 ms 158.603 ms
14 82-140-42-33.static.servage.net (82.140.42.33) 160.486 ms 160.804 ms 160.162 ms


And...I hit your site with no problem. It defaults to the SmartPartner module. Is that correct?

So, if you are still not getting there, it's your ISP. They are not updating their DNS (BIND isn't running enough) servers on a regular basis. I am surprised you can't hit the site with IP address only...I just checked.

Okay, if you are a dedicated IP, your server console doesn't DNS you that way. Your dedicated IP goes to your control panels default - "This site isn't set up yet" So, my guess is, you may be a dedicated IP, but you are on a virtual environment of some sort, and addressing by IP is captured by the server software and redirected to the console default pages...You might verify, when you can actually get in, the DNS records to make sure they are all correct.

Good luck!
John Horne - a.k.a. - VelocityWebDev, Seventhseal, CreepingDeath
**********************************
VelocityWebDev Tech BLOG
VelocityWebHost Hosting and Design

7
svaha
Re: Can't get to my site.
  • 2007/2/27 17:05

  • svaha

  • Just can't stay away

  • Posts: 896

  • Since: 2003/8/2 2


Yes my startpage is the smartpartner module.

And it's a virtual environment, servage works with virtual hosts.

When I look at my dns settings through the control panel I see :

@.amevita.eu A-record 82.140.42.33
*.amevita.eu A-record 77.232.70.123

Should I set the first record also to 77.232.70.123 then?

8
seventhseal
Re: Can't get to my site.

yes, that is the ticket. I just tested your site. It makes me wonder if your move has really happened? You might check with your host provider to make sure they have transferred everything - as I read what you have provided, it looks like your site is still resolving to the old IP, and the new IP will present the site, so right now, I have no idea what the DNS servers think is right! Yikes, make the change and update. The only problem is you may have 72 hours before proper propagation. However, I'm seeing both IP now...
John Horne - a.k.a. - VelocityWebDev, Seventhseal, CreepingDeath
**********************************
VelocityWebDev Tech BLOG
VelocityWebHost Hosting and Design

9
Stewdio
Re: Can't get to my site.
  • 2007/2/27 21:49

  • Stewdio

  • Community Support Member

  • Posts: 1560

  • Since: 2003/5/7 1


When ever I've moved a site, which has been quite a few times, I always wait a couple of days for things to settle down.

I don't announce the site move until well after it's happened. When I know for sure the the new DNS record has taken affect, I get rid of the old record. A couple days later, the old record is out of most DNS cache servers around the globe and then I announce the site move, if it's even all that neccessary. Most people don't care that you changed host providers. Some do, some don't.

My way is a little slower, but it seems to have the least amount of impact on end users.
XOOPS Community Support

10
svaha
Re: Can't get to my site.
  • 2007/3/23 15:34

  • svaha

  • Just can't stay away

  • Posts: 896

  • Since: 2003/8/2 2


Quote:

Stewdio wrote:
When ever I've moved a site, which has been quite a few times, I always wait a couple of days for things to settle down.

I don't announce the site move until well after it's happened. When I know for sure the the new DNS record has taken affect, I get rid of the old record. A couple days later, the old record is out of most DNS cache servers around the globe and then I announce the site move, if it's even all that neccessary. Most people don't care that you changed host providers. Some do, some don't.

My way is a little slower, but it seems to have the least amount of impact on end users.


Well I did not actually move my site, just got me a dedicated IP and assigned my site to this dedicated IP (instead of the shared IP I had)
I tried the options mentioned here and waited for more then a week, but no result, I still could not get to my site.
So I went back to the shared IP and pointed my a-records to the servage name servers. After a few hours I could access my site.

Login

Who's Online

328 user(s) are online (262 user(s) are browsing Support Forums)


Members: 0


Guests: 328


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits