client snuck out in the dark of night

[Binky]

Just for the record, the deadbeat client discussed in the threads
disable sending but not receiving - possible? (http://www.aota.net/forums/showthread.php?s=&threadid=17986)
chmod site - how? (http://www.aota.net/forums/showthread.php?s=&threadid=18042)
responded to my disabling of his site by changing nameservers.

It's been four days but as of noon today (Oct 22) the old site with the 403 page is still showing up, at least for me.

The site's at http://simonpatrich.com

[Bob]

Hello,

I am seeing a normal web site and pings to it resolve to 204.174.223.194.

Are you sure you are not seeing cached pages ?

-Bob

[Binky]

Are you sure you are not seeing cached pages ? Hmmm. I guess I must be. When I paste 204.174.223.194 into my browser I get a page that says The URL you have requested does not have a web site associated with it.

[Bob]

Hi again,

I get the same thing when accessing via IP address which may be the result of the new host not allowing direct IP access or using shared IPs.

However when using the domain name, with and w/o 'www', I see a web site with the Gallery Name displayed at the top and a picture of what I assume is the Gallery...

-Bob

[Binky]

This caching thing has always been a bit of a mystery to me. Previously, when domains changed nameservers (clients having moved on, amicably I should add) the new site would show up on my Mac almost right away and sometimes days later on my PC - both connected by a router to the same ISP. I'd love to have that explained to me.

In this case it's been four days and I'm still seeing the FQ site on both machines.

I can't tell how upset this whole business has made me. This was one of my first clients. We became good friends (I thought). But he was always late paying me and in the last couple of years getting money from him was like pulling teeth. Two or three weeks ago I visited him at his business and after a friendly chat I asked when he would pay me. His balance had reached over $600. He just about threw me out of the gallery. We exchanged a few emails and I warned him if I wasn't paid within a week I'd disable his site till I was paid. He agreed to a payment plan and then changed nameservers instead.

[Bob]

Hi again,

First thing I would do would be to ping or tracert the domain name and see what IP address it resolves to...

If a ping or tracert resolves to the IP address mentioned above then you may want to force a browser reload/refesh by using SHIFT+reload, CTRL+F5 (or in some cases Shift+CTRL+Reload).

In really persistent instances, when you know it is a machine cache issue, rebooting the machine may become necessary...

If the ping/tracert resolves to the old FutureQuest IP your ISP may be very slow in updating their DNS cache at the present time, or you may be running a local DNS cache with the old IP entered...

-Bob

[Binky]

ping simonpatrich.com

Pinging simonpatrich.com [69.5.28.31] with 32 bytes of data:

Reply from 69.5.28.31: bytes=32 time=123ms TTL=46
Reply from 69.5.28.31: bytes=32 time=122ms TTL=46
Reply from 69.5.28.31: bytes=32 time=120ms TTL=46
Reply from 69.5.28.31: bytes=32 time=121ms TTL=46

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



tracert simonpatrich.com

Tracing route to simonpatrich.com [69.5.28.31]
over a maximum of 30 hops:

1 80 ms 12 ms 12 ms d64-180-160-254.bchsia.telus.net [64.180.160.254]
2 11 ms 11 ms 11 ms d64-180-160-254.bchsia.telus.net [64.180.160.254]
3 11 ms 11 ms 11 ms 208.181.240.90
4 11 ms 21 ms 11 ms vancbc01gr01.bb.telus.com [154.11.4.97]
5 62 ms 62 ms 62 ms vancbc01br01.bb.telus.com [154.11.10.89]
6 63 ms 62 ms 62 ms 204.225.243.42
7 66 ms 62 ms 62 ms wnpgmb38br00.bb.telus.com [154.11.10.158]
8 62 ms 62 ms 62 ms 204.225.243.157
9 * * * Request timed out.
10 61 ms 62 ms 62 ms chcgildtgr00.bb.telus.com [154.11.11.18]
11 61 ms 68 ms 62 ms 66.192.252.89
12 62 ms 61 ms 63 ms 66.192.244.37
13 83 ms 84 ms 86 ms core-01-so-1-0-0-0.dlfw.twtelecom.net [66.192.255.89]
14 112 ms 112 ms 113 ms dist-01-so-0-0-0-0.mtld.twtelecom.net [66.192.243.6]
15 112 ms 112 ms 113 ms dist-01-ge-2-2-0-0.mtld.twtelecom.net [66.192.243.145]
16 122 ms 121 ms 121 ms core-x-01-2.futurequest.net [69.5.31.253]
17 123 ms 122 ms 121 ms x31.futurequest.net [69.5.28.31]

Trace complete.

The ex-client uses the same ISP as I do. (Telus.net) Does this mean he'd also be seeing the FQ site?