Web Host issue - slow loading.

[csmager]

Helping a friend out with a problem with a website. Fairly certain it's the web host at fault, but they deny any knowledge. Trying to convince them there is an issue is going to be an effort, but first, I want to see if anyone can replicate the issue. Then what I'd really like is an explanation of how it could happen!

The site in question:

www.greenroomsports.co.uk

And exact copy is hosted here:

www.csmager.net/grs

The first link, when you first load it, can take up to 20 seconds. Just sitting there, waiting for the server to respond. Then it all comes at once - site loads in a couple of seconds.

The second link, same site, different host. Loads in a couple of seconds.

Any ideas how this kind of issue could be caused? I'd be surprised no one else has complained about the same issue on their sites... unless it just applies to this one!

Thanks all!

 

[tolien]

Both sites load quickly here, but if it loads quickly once you get to the server it sounds like you've got a DNS issue.

 

[csmager]

Happens on my connection here (idnet), happens on my connection at my flat in London (Be), happens on my friend's connection in their office (unknown), happens on my friend's connection at his house (Sky BB).

In the bottom left of IE while it's sitting there it says the IP address (192.168.192.23). So I don't think it's DNS. It seems to be the server taking forever to match the host header to the folder it's meant to serve up. Once the session's started it seems fine after that.

I can then close IE and load it up again, and it'll take 20seconds again most of the time.

 

[daz]

192.168.x.x is reserved isn't it?

I reckon you have an A record for www.yourdomain.com pointing at 89.31.232.37

But the yourdomain.com (without the www) pointing at the private range... which isn't going to work...

 

[csmager]

Think that's nail on the head. Cheers daz. Did think it was odd that 192.168 was showing up in my browser, but it connected eventually so I assumed it must've been ok.

Turns out there're two DNS records. One pointed at the local address and one pointed at the actual address - no idea how they managed to screw that up. Evidently it fails the first one and retries on the second and succeeds. A DNS checking site gives this reponse:

- Error connecting to HTTP server www.greenroomsports.co.uk [192.168.192.23] port 80: timed out waiting for connection
- Checking HTTP server www.greenroomsports.co.uk [89.31.232.37] HTTP server www.greenroomsports.co.uk[89.31.232.37] answers on port 80

No option to change it the limited DNS control panel, so I'll get onto them now I know what the issue is.

Thanks again.

 

[mynsa]

to be honest if they know what they were doing they should have spotted that error when you first reported the issue.

Who puts local addresses for a domain on a dns server used on the inet that obviously isnt going to route...