is Microstockgroup down for you?

06/01/2009 04:57:09 PM · #1

Hmm then that has me stumped, I guess it could be a local DNS server issue (to the users ISP I mean), do you have any other people you can contact that have reported the problem? I would try and get at least one more tracert from someone else and see if they are also trying to resolve to the same incorrect IP.

I do remember a couple of years back having something slightly similar but mine was that practically all visitors could not connect to one of my sites when I changed hosts, the DNS had just not updated correctly but only on this one site and I ended up resetting the DNS to defaults, leaving it for 72 hours and then setting them back to my name servers this cured the problem but the site was offline for almost a week.

06/01/2009 04:49:12 PM · #2

Originally posted by Mark-A:

I see you mention you have gone for a VPS was this very recently? Only they say it can take up to 72 hours for DNS changes to fully resolve but I have known them to take longer (although this is very rare).

no it was almost a year ago.

06/01/2009 04:41:56 PM · #3

06/01/2009 04:39:30 PM · #4

Here is what i got for the webhost. They seem to think it is on the ISP side, maybe they are right?!

We have reviewed the provided results and it seems that the domain name is not resolved properly on your user's end. As you can see each ping/traceroute returns an incorrect IP address.

PING //www.microstockgroup.com/ (80.156.86.78): 56 data bytes

traceroute: Warning: //www.microstockgroup.com/ has multiple addresses; using 62.157.140.133

We have checked the DNS zone for your domain name but the above mentioned IP address are not present. That leads us to the though that either the used Internet Service Provider is not able to obtain the correct values or there is local zone which has multiple IP address for your domain name on the user's computer.

As you can see from the online DNS checker, the correct IP address for your domain name is 69.65.98.2. The traceroute to the IP address appears to reach the Data Center where the VPS machine are hosted ( defenderhosting.com ).

//www.iptools.com/dnstools.php?tool=dns&user_data=microstockgroup.com&type=A

Since we do not have control over your user network, I will recommend you to advise him/her to contact his/her Internet Service Provider in order to solve the resolving issue on her/his end.

06/01/2009 04:03:25 PM · #5

Originally posted by leaf:

thanks for the help all.

all this SHE talk.. are you talking about me??? I am HE

Ha. That's Paul's fault. When he used she I figured he just knew something about you that I didn't. :P

06/01/2009 03:40:09 PM · #6

thanks for the help all.

all this SHE talk.. are you talking about me??? I am HE

anyhow.
I got a tracert report from the one person who had problems with the site and i will send that to my webhost and see if they can sniff out any problems.

I having purchased a virtual private server, but I suppose that isn't enough to give me a private IP. I am using siteground now, but am thinking about switching over to Bluehost.

06/01/2009 04:37:03 AM · #7

It is true what Richard says but even when running from a dedicated server you can still share the same IP (albeit with your own sites) I run 20 odd sites from 5 IPs the only ones I allocate a unique IP for are those that are https (which then has to have a dedicated IP anyway). The main flaw in your plan though Richard is that most webhosts are allocated a range of IPs to use so even getting a dedicated one doesn't stop you from being blocked in the scenario that GeneralE gives.

ETA: Spelling :(

Message edited by author 2009-06-01 04:38:54.

Canon 12x IS USM (S3 IS built-in Lens) -- 36-432mm (35mm EQ)

06/01/2009 04:26:38 AM · #8

Originally posted by GeneralE:

Originally posted by yanko:

Originally posted by GeneralE:

Originally posted by leaf:
I wonder if it could be that I am sharing an IP address with some other site that the IP in some locations decided to block.

Try to find out if the user is behind a firewall, especially a work-related one.

I think sometimes a corporate IT admin or an ISP will block a whole range of IP addresses, not just the particular one hosting your site, so you could get blocked out because of some other site hosted by your ISP.

PS: the site seems to load up OK for me from Oakland, CA -- it was working yesterday as well.

Even if that's not the case getting a dedicated IP just makes good business sense.

She HAS a dedicated IP address -- that's how the DNS servers find her files when someone types in the name of the website.

But the person who has the trouble, their ISP may be blocking (for example) all IP addresses between 000.000.000.128 through 000.000.000.254 because several domains resolving to addresses within that range are objectionable. If her IP address happens to be 000.000.000.167 it could get blocked along with all the others.

No she doesn't appear to have a dedicated IP. It looks like she is sharing one. I looked up her IP address via IP check and when I try it in a browser (i.e. //69.65.98.2/) her website doesn't load. If she had a dedicated IP it should take me straight to her site just like when I typed in her domain name. She is on a shared hosting plan which is cheaper than a dedicated hosting plan but you don't get the unique IP address. It typically only costs around $1-$2 dollars a month to own your own IP. She should get it. It makes sense to do so. It's just too easy to get blacklisted by an ISP or penalized by a search engines when you share your IP with hundreds of other web sites. As a business why risk that?

Message edited by author 2009-06-01 04:27:47.

GeneralE

Canon PowerShot S3 IS

06/01/2009 02:40:18 AM · #9

Originally posted by yanko:

Originally posted by GeneralE:

Originally posted by leaf:
I wonder if it could be that I am sharing an IP address with some other site that the IP in some locations decided to block.

Try to find out if the user is behind a firewall, especially a work-related one.

I think sometimes a corporate IT admin or an ISP will block a whole range of IP addresses, not just the particular one hosting your site, so you could get blocked out because of some other site hosted by your ISP.

PS: the site seems to load up OK for me from Oakland, CA -- it was working yesterday as well.

Even if that's not the case getting a dedicated IP just makes good business sense.

She HAS a dedicated IP address -- that's how the DNS servers find her files when someone types in the name of the website.

But the person who has the trouble, their ISP may be blocking (for example) all IP addresses between 000.000.000.128 through 000.000.000.254 because several domains resolving to addresses within that range are objectionable. If her IP address happens to be 000.000.000.167 it could get blocked along with all the others.

Canon 12x IS USM (S3 IS built-in Lens) -- 36-432mm (35mm EQ)

06/01/2009 01:20:03 AM · #10

Originally posted by GeneralE:

Originally posted by leaf:
I wonder if it could be that I am sharing an IP address with some other site that the IP in some locations decided to block.

Try to find out if the user is behind a firewall, especially a work-related one.

I think sometimes a corporate IT admin or an ISP will block a whole range of IP addresses, not just the particular one hosting your site, so you could get blocked out because of some other site hosted by your ISP.

PS: the site seems to load up OK for me from Oakland, CA -- it was working yesterday as well.

Even if that's not the case getting a dedicated IP just makes good business sense.

Message edited by author 2009-06-01 01:20:18.

GeneralE

Canon PowerShot S3 IS

05/31/2009 10:16:47 PM · #11

Originally posted by leaf:

I wonder if it could be that I am sharing an IP address with some other site that the IP in some locations decided to block.

Try to find out if the user is behind a firewall, especially a work-related one.

I think sometimes a corporate IT admin or an ISP will block a whole range of IP addresses, not just the particular one hosting your site, so you could get blocked out because of some other site hosted by your ISP.

PS: the site seems to load up OK for me from Oakland, CA -- it was working yesterday as well.

Message edited by author 2009-05-31 22:18:11.

05/31/2009 09:06:01 PM · #12

FYI, it's working for me now.

05/31/2009 06:46:45 PM · #13

ah yeah, i see :)

anyone want to offer up their tracert report? or just the problem area? I have sent the info to the person who cannot access the site. Hopefully he is able to give some info as well

Message edited by author 2009-05-31 18:46:58.

05/31/2009 05:26:35 AM · #14

Sorry Leaf I mean't ask those with problems for a tracert report :)

05/31/2009 04:59:24 AM · #15

except the site works for me, so my tracert would look good.

I wonder if it could be that I am sharing an IP address with some other site that the IP in some locations decided to block.

05/30/2009 07:41:10 PM · #16

Get a tracert from the user mate and present that to your host it will give them some idea of where the problem lies.

Incase you are not aware how to:

Open a DOS command prompt and type: tracert www.microstockgroup.com

It will give you a readout like this:

Tracing route to microstockgroup.com [69.65.98.2]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 25 ms 59 ms 20 ms 10.29.40.1
3 25 ms 17 ms 21 ms bmly-cam-1a-v100.network.virginmedia.net [80.1.226.101]
4 55 ms 56 ms 65 ms bmly-t3core-1a-ge-010-0.network.virginmedia.net [80.1.225.41]
5 14 ms 31 ms 18 ms pop-bb-a-so-320-0.network.virginmedia.net [212.43.162.57]
6 51 ms 22 ms 17 ms bre-bb-b-as4-0.network.virginmedia.net [62.255.81.238]
7 40 ms 30 ms 12 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
8 23 ms 12 ms 34 ms ldn-b2-link.telia.net [213.248.100.97]
9 22 ms 15 ms 29 ms ldn-bb2-link.telia.net [80.91.252.13]
10 109 ms 97 ms 111 ms ash-bb1-link.telia.net [80.91.251.209]
11 100 ms 99 ms 86 ms hurricane-ic-124167-ash-bb1.c.telia.net [213.248.98.94]
12 113 ms 110 ms 107 ms 209.51.161.10
13 110 ms 141 ms 131 ms r01.iad.keepitsecure.net [69.65.112.1]
14 105 ms 101 ms 112 ms aggr-sw2.iad.defenderhosting.com [69.65.112.94]
15 113 ms 112 ms * eqash9.keepitsecure.net [69.65.115.47]
16 99 ms 115 ms 109 ms vps125.sgvps.net [69.65.98.2]

Trace complete.

Olympus OM-D E-M5 Mark III

05/30/2009 07:27:26 PM · #17

Originally posted by yanko:

It dosn't load for me. I'm in Austin, Texas. The error I get is Network Timeout error. The server at www.microstockgroup.com is taking too long to respond.

hmm.. well nice to find one problem spot... anyone know how to go about complaining to the web host about this? I can't really just say 'someone' has a problem. I need to have something they can see, or something I can report.

GinaRothfels

Olympus 8mm f/1.8 M.Zuiko Digital ED Fisheye PRO Lens

05/30/2009 07:05:55 PM · #18

Working in South Africa.

Mal37

Canon EF-S 18-55mm f/3.5-5.6

05/30/2009 06:49:21 PM · #19

Works in Buffalo, NY

fldave

Pentax K5II

Pentax DA 18-135mm F3.5-5.6ED AL [IF] WR DC

05/30/2009 06:38:14 PM · #20

Loaded quickly in South Florida.

Gallatin

Nikon D4s

Nikon AF-S NIKKOR 24-70mm f/2.8G ED

05/30/2009 06:19:01 PM · #21

Worked great in the Big Sky Country/USA

05/30/2009 05:09:31 PM · #22

It's loading here mate but it's very, very slow

UK based

ETA: Hmmm when I ping it's not showing it to be as slow as the site is actually performing:

Pinging microstockgroup.com [69.65.98.2] with 32 bytes of data:
Reply from 69.65.98.2: bytes=32 time=123ms TTL=53
Reply from 69.65.98.2: bytes=32 time=97ms TTL=53
Reply from 69.65.98.2: bytes=32 time=102ms TTL=53
Reply from 69.65.98.2: bytes=32 time=104ms TTL=53

Ping statistics for 69.65.98.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 97ms, Maximum = 123ms, Average = 106ms

Message edited by author 2009-05-30 17:13:00.

05/30/2009 05:03:16 PM · #23

It dosn't load for me. I'm in Austin, Texas. The error I get is Network Timeout error. The server at www.microstockgroup.com is taking too long to respond.