Odd indeed. I'm on a BT domestic connection and,

The site fails to load in Firefox or IE, with IP or domain.
NSLOOKUP is fine, resolves to 208.43.255.194
PING fails.
TRACERT fails at po1.fcr01.wdc01.washingtondc-datacenter.com

Who is your host for the site?

It's fine on VM.

It's can't be DNS if the IP is also failing.

Possibly suggests peering issue rather than anything to do with DNS from our end.

Tracing route to imaging-resource.com [208.43.255.194]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ge-0-2-0-7.fhw-cr02.plus.net [84.93.216.85]
2 6 ms 6 ms 6 ms at0-3-0-pte-gw2.plus.net [212.159.1.91]
3 7 ms 7 ms 7 ms cr1-linx-peer.lon005.internap.net [195.66.224.44
]
4 90 ms 91 ms 90 ms cr1.wdc005.inappnet.cr1.lon005.internap.net [66.
79.147.37]
5 91 ms 90 ms 91 ms cr1-cr2.wdc005.internap.net [66.79.146.201]
6 87 ms 87 ms 87 ms core2.wdc002.inappnet-62.cr1.wdc005.internap.net
[66.79.151.130]
7 87 ms 88 ms 87 ms border1.te7-2-bbnet2.wdc008.pnap.net [216.52.127
.98]
8 87 ms 87 ms 87 ms te1-1.cer01.wdc01.washingtondc-datacenter.com [6
6.151.100.66]
9 87 ms 87 ms 87 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208
.43.118.134]
10 86 ms 104 ms 87 ms ir.theimagingresource.com [208.43.255.194]

Trace complete.

Hi James

Very odd, so why is it failing for some folks but not others??? I know the few folk trying does not make an analysis but seems that BT & PlusNet users are the ones having trouble.

We don't share our IP Addresses with BT, so that shouldn't be related.

Odd - this my tracert
Tracing route to imaging-resource.com [208.43.255.194]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 54 ms 40 ms 38 ms lo0.plusnet.thn-ag1.plus.net [195.166.128.101]
3 39 ms 38 ms 40 ms vl703.thn-gw1.plus.net [84.92.4.241]
4 38 ms 40 ms 38 ms vl22.pte-gw1.plus.net [212.159.4.11]
5 38 ms 38 ms 39 ms te2-4.pte-gw2.plus.net [212.159.1.102]
6 39 ms 39 ms 37 ms cr1-linx-peer.lon005.internap.net [195.66.224.44]
7 122 ms 122 ms 123 ms cr1.wdc005.inappnet.cr1.lon005.internap.net [66.79.147.37]
8 124 ms 123 ms 127 ms cr1-cr2.wdc005.internap.net [66.79.146.201]
9 117 ms 120 ms 123 ms core2.wdc002.inappnet-62.cr1.wdc005.internap.net [66.79.151.130]
10 121 ms 119 ms 120 ms border1.te7-2-bbnet2.wdc008.pnap.net [216.52.127.98]
11 119 ms 118 ms 119 ms te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66]
12 298 ms 180 ms 119 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.

site works from here, from a bt up to 8 mbit connection north london: (tested 11.44am)

Tracing route to ir.theimagingresource.com [208.43.255.194]
over a maximum of 30 hops:

1 52 ms 90 ms 98 ms BThomehub.home [192.168.1.254]
2 30 ms 31 ms 31 ms esr9.faraday3.broadband.bt.net [217.47.166.140]
3 31 ms 31 ms 31 ms 217.47.166.13
4 31 ms 31 ms 30 ms 217.47.45.170
5 31 ms 30 ms 31 ms 217.41.177.9
6 31 ms 33 ms 33 ms 217.41.177.66
7 32 ms 31 ms 30 ms 217.41.177.126
8 30 ms 30 ms 31 ms 217.41.177.38
9 32 ms 32 ms 30 ms 217.47.93.50
10 31 ms 31 ms 30 ms core2-pos12-7.faraday.ukcore.bt.net [194.72.4.141]
11 32 ms 32 ms 32 ms core2-pos0-1-1-0.ealing.ukcore.bt.net [62.6.204.85]
12 32 ms 32 ms 31 ms 194.72.17.122
13 32 ms 33 ms 42 ms t2c1-ge8-0-0.uk-eal.eu.bt.net [166.49.168.17]
14 106 ms 107 ms 107 ms t2c1-p4-0-0.us-ash.eu.bt.net [166.49.164.225]
15 109 ms 108 ms 108 ms te1-2.cer01.wdc01.washingtondc-datacenter.com [206.223.115.185]
16 108 ms 108 ms 108 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
17 106 ms 106 ms 107 ms ir.theimagingresource.com [208.43.255.194]

Trace complete.

edit ip range: range217-44.btcentralplus.com

Edited by ggremlin (Fri 25-Sep-09 12:12:25)

From a Plusnet connection
Target Name: ir.theimagingresource.com
IP: 208.43.255.194
Date/Time: 25/09/2009 13:54:23

1 1 ms menu [192.168.1.254]
2 17 ms lo0-plusnet.pcl-ag04.plus.net [195.166.128.134]
3 16 ms gi1-6-604.pcl-gw02.plus.net [84.92.0.229]
4 16 ms te2-2.thn-gw2.plus.net [212.159.0.190]
5 16 ms vl23.pte-gw2.plus.net [212.159.4.28]
6 15 ms cr1-linx-peer.lon005.internap.net [195.66.224.44]
7 104 ms cr1.wdc005.inappnet.cr1.lon005.internap.net [66.79.147.37]
8 101 ms cr1-cr2.wdc005.internap.net [66.79.146.201]
9 101 ms core2.wdc002.inappnet-62.cr1.wdc005.internap.net [66.79.151.130]
10 94 ms border1.te7-2-bbnet2.wdc008.pnap.net [216.52.127.98]
11 96 ms te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66]
12 98 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
13 96 ms ir.theimagingresource.com [208.43.255.194]

I thought in case time will heal this to leave it till now try to access the site again and it still fails.....................so odd?