Can a few people please check the following for me?

[zaktoo]

Hi all

Is there anyone here who can't get to both www.carfolio.com and www.aaifotostock.com , or who can get to the former but not the latter please? I'm having odd problems which I can't diagnose adequately from here as both work fine for me and the client (the latter site) isn't pleased ;-)

Thanks!

Ciao

Zak

[puggit]

I can get to both, but the addresses took around 5 secs to work - much longer then usual

[zaktoo]

puggit said:

I can get to both, but the addresses took around 5 secs to work - much longer then usual

Thanks, will take a look at the resolve times issue

Cheers

Zak

[mattley]

Works fine here, what problem is your client having?

[vipers]

Just tried, both come up in about 2 seconds.

[zaktoo]

mattley said:

Works fine here, what problem is your client having?

Client is getting a bad gateway timeout to the latter site, I suspect it is due to the cache between her & the site having cached the old dns entry for the domain. She's got at least a transparent proxy and who knows what else - I can't get to her site (not the web site, her physical location I mean) either, she's moved far away...

Thanks, I appreciate the feedback

Edit: tyops

Edited by zaktoo on Monday 10th July 18:10

Edited by zaktoo on Monday 10th July 18:15

[mattley]

Hmmm


Both work fine in my browser but the pings are a little dodgy

Ping said:

C:Documents and SettingsMatt>ping www.aaifotostock.com

Pinging mail.aaifotostock.com [83.245.34.22] with 32 bytes of data:

Reply from 83.245.34.22: bytes=32 time=9ms TTL=57
Request timed out.
Reply from 83.245.34.22: bytes=32 time=7ms TTL=57
Reply from 83.245.34.22: bytes=32 time=9ms TTL=57

Ping statistics for 83.245.34.22:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 9ms, Average = 8ms

C:Documents and SettingsMatt>ping www.carfolio.com

Pinging www.carfolio.com [83.245.34.22] with 32 bytes of data:

Reply from 83.245.34.22: bytes=32 time=8ms TTL=57
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 83.245.34.22:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 8ms, Average = 8ms

C:Documents and SettingsMatt>ping www.carfolio.com

Pinging www.carfolio.com [83.245.34.22] with 32 bytes of data:

Request timed out.
Request timed out.
Reply from 83.245.34.22: bytes=32 time=8ms TTL=57
Request timed out.

Ping statistics for 83.245.34.22:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 8ms, Average = 8ms

C:Documents and SettingsMatt>ping www.aaifotostock.com

Pinging mail.aaifotostock.com [83.245.34.22] with 32 bytes of data:

Request timed out.
Request timed out.
Reply from 83.245.34.22: bytes=32 time=7ms TTL=57
Reply from 83.245.34.22: bytes=32 time=8ms TTL=57

Ping statistics for 83.245.34.22:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 8ms, Average = 7ms

Tracert is a little inconsistent too,

tracert said:

C:Documents and SettingsMatt>tracert 83.245.34.22

Tracing route to server11.register1.net [83.245.34.22]
over a maximum of 30 hops:

1 6 ms 6 ms 28 ms 10.69.228.1
2 8 ms 5 ms 10 ms wtfd-t2cam1-b-ge910.inet.ntl.com [80.3.2.149]
3 18 ms 7 ms 9 ms wtfd-t2core-b-ge-wan61.inet.ntl.com [80.3.1.133]

4 8 ms 16 ms 7 ms pop-bb-b-so-710-0.inet.ntl.com [80.3.1.137]
5 12 ms 11 ms 8 ms pop-bb-a-ge-000-0.inet.ntl.com [213.105.174.229]

6 7 ms 8 ms 15 ms 195.50.91.69
7 7 ms 7 ms 8 ms ae-25-56.car5.london1.level3.net [4.68.116.179]

8 * * * Request timed out.
9 * * 11 ms server11.register1.net [83.245.34.22]

Trace complete.

C:Documents and SettingsMatt>tracert 83.245.34.22

Tracing route to server11.register1.net [83.245.34.22]
over a maximum of 30 hops:

1 7 ms 6 ms 7 ms 10.69.228.1
2 6 ms 6 ms 7 ms wtfd-t2cam1-b-ge910.inet.ntl.com [80.3.2.149]
3 6 ms 27 ms 7 ms wtfd-t2core-b-ge-wan61.inet.ntl.com [80.3.1.133]

4 10 ms 8 ms 7 ms pop-bb-b-so-710-0.inet.ntl.com [80.3.1.137]
5 8 ms 8 ms 7 ms pop-bb-a-ge-000-0.inet.ntl.com [213.105.174.229]

6 * * 28 ms 195.50.91.69
7 7 ms 7 ms 7 ms ae-25-52.car5.london1.level3.net [4.68.116.51]
8 9 ms 18 ms 9 ms server11.register1.net [83.245.34.22]

Trace complete.

could be some over aggressive timeouts on one of their gateways.

[JamieBeeston]

Both work fine and rapid here.

neither have A records for domain.com tho, I don't know if this is deliberate or not.

J

[zaktoo]

JamieBeeston said:

Both work fine and rapid here.

neither have A records for domain.com tho, I don't know if this is deliberate or not.

J

Yes, I do prefer not having A records for the domain itself - it shouldn't cause issues, should it?

[JamieBeeston]

zaktoo said:

JamieBeeston said:

Both work fine and rapid here.

neither have A records for domain.com tho, I don't know if this is deliberate or not.

J

Yes, I do prefer not having A records for the domain itself - it shouldn't cause issues, should it?

Might give grief for email as [e-mail] may result in domain.com does not exist.

Past that, it shouldnt really.

J

[JamieBeeston]

mattley said:

Hmmm


Both work fine in my browser but the pings are a little dodgy

Ping said:

Cocuments and SettingsMatt>ping www.aaifotostock.com

Pinging mail.aaifotostock.com [83.245.34.22] with 32 bytes of data:

Reply from 83.245.34.22: bytes=32 time=9ms TTL=57
Request timed out.
Reply from 83.245.34.22: bytes=32 time=7ms TTL=57
Reply from 83.245.34.22: bytes=32 time=9ms TTL=57

Ping statistics for 83.245.34.22:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 9ms, Average = 8ms

Cocuments and SettingsMatt>ping www.carfolio.com

Pinging www.carfolio.com [83.245.34.22] with 32 bytes of data:

Reply from 83.245.34.22: bytes=32 time=8ms TTL=57
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 83.245.34.22:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 8ms, Average = 8ms

Cocuments and SettingsMatt>ping www.carfolio.com

Pinging www.carfolio.com [83.245.34.22] with 32 bytes of data:

Request timed out.
Request timed out.
Reply from 83.245.34.22: bytes=32 time=8ms TTL=57
Request timed out.

Ping statistics for 83.245.34.22:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 8ms, Average = 8ms

Cocuments and SettingsMatt>ping www.aaifotostock.com

Pinging mail.aaifotostock.com [83.245.34.22] with 32 bytes of data:

Request timed out.
Request timed out.
Reply from 83.245.34.22: bytes=32 time=7ms TTL=57
Reply from 83.245.34.22: bytes=32 time=8ms TTL=57

Ping statistics for 83.245.34.22:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 8ms, Average = 7ms

Tracert is a little inconsistent too,

tracert said:

Cocuments and SettingsMatt>tracert 83.245.34.22

Tracing route to server11.register1.net [83.245.34.22]
over a maximum of 30 hops:

1 6 ms 6 ms 28 ms 10.69.228.1
2 8 ms 5 ms 10 ms wtfd-t2cam1-b-ge910.inet.ntl.com [80.3.2.149]
3 18 ms 7 ms 9 ms wtfd-t2core-b-ge-wan61.inet.ntl.com [80.3.1.133]

4 8 ms 16 ms 7 ms pop-bb-b-so-710-0.inet.ntl.com [80.3.1.137]
5 12 ms 11 ms 8 ms pop-bb-a-ge-000-0.inet.ntl.com [213.105.174.229]

6 7 ms 8 ms 15 ms 195.50.91.69
7 7 ms 7 ms 8 ms ae-25-56.car5.london1.level3.net [4.68.116.179]

8 * * * Request timed out.
9 * * 11 ms server11.register1.net [83.245.34.22]

Trace complete.

Cocuments and SettingsMatt>tracert 83.245.34.22

Tracing route to server11.register1.net [83.245.34.22]
over a maximum of 30 hops:

1 7 ms 6 ms 7 ms 10.69.228.1
2 6 ms 6 ms 7 ms wtfd-t2cam1-b-ge910.inet.ntl.com [80.3.2.149]
3 6 ms 27 ms 7 ms wtfd-t2core-b-ge-wan61.inet.ntl.com [80.3.1.133]

4 10 ms 8 ms 7 ms pop-bb-b-so-710-0.inet.ntl.com [80.3.1.137]
5 8 ms 8 ms 7 ms pop-bb-a-ge-000-0.inet.ntl.com [213.105.174.229]

6 * * 28 ms 195.50.91.69
7 7 ms 7 ms 7 ms ae-25-52.car5.london1.level3.net [4.68.116.51]
8 9 ms 18 ms 9 ms server11.register1.net [83.245.34.22]

Trace complete.

could be some over aggressive timeouts on one of their gateways.

I'd say that's your DSL / Cable company filtering ICMP

External Ping from Different Network said:

--- mail.aaifotostock.com ping statistics ---
1000 packets transmitted, 1000 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.879/1.253/2.808/0.273 ms

External Ping from Alternate Different Network said:

--- mail.aaifotostock.com ping statistics ---
1000 packets transmitted, 1000 packets received, 0% packet loss
round-trip min/avg/max = 1.0/1.2/1.9 ms

That much real packet loss would result in the site barely loading.

J

[mattley]

JamieBeeston said:

I'd say that's your DSL / Cable company filtering ICMP

I don't think NTL fiter, I'd have noticed it by now, but I only started using them recently so if there's anything I should know...

[JamieBeeston]

mattley said:

JamieBeeston said:

I'd say that's your DSL / Cable company filtering ICMP

I don't think NTL fiter, I'd have noticed it by now, but I only started using them recently so if there's anything I should know...

hehe bless them

They use Transparent Proxies to force your web traffic via their Cache servers to save on b/w

Most routers will drop ICMP first if they get busy, so could just be one of the routers your route traverses was a little loaded at the time

J

[zaktoo]

JamieBeeston said:

mattley said:

JamieBeeston said:

I'd say that's your DSL / Cable company filtering ICMP

I don't think NTL fiter, I'd have noticed it by now, but I only started using them recently so if there's anything I should know...

They use Transparent Proxies to force your web traffic via their Cache servers to save on b/w

I hate that, it's a real PITA when diagnosing issues, especially to something that isn't supposed to be live until operational. All our South African ISPs do it though

As for the origianl reason for the thread, thanks everyone, it's working now. The ( grrrr ) transparent proxy that my client was on has finally decided to update its cached dns entries and it's now ok for her too...

Ciao

Zak