[QUOTE=SubSpace]
Or just set some nameservers from another ISP that are public. A nameserver that caches for 14 days regardless of the TTL is plain useless.
[/QUOTE]
I’m not sure I understand this. I can set my nameservers to one other than those my ISP uses? How/Where do I do that exactly?
Start → Setting → Network and Dial → Up Connections → Local Area Connection → Properties → Internet Protocol(TCP/IP) → > Properties → Use the following DNS Server Addresses
Thank you Interlink. Do you happen to know of any ‘open public’ DNS servers out there with less than a 14 days caching threshold? 
You can use the following DNSs for testing purposes:
209.208.123.124
209.208.123.125
Due latency, I recommend DNS servers “located” few hops from your computer.
Check hops/latency using command tracert. E.g.
tracert 209.208.123.124
so would this be good?
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:>tracert 209.208.123.124
Tracing route to mrcs4-ip-124.atlantic.net [209.208.123.124]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 8 ms 10.40.160.1
3 7 ms 7 ms 8 ms srp2-0.dytnoh1-rtr2.woh.rr.com [24.29.161.148]
4 15 ms 17 ms 15 ms son0-0-3.ncntoh1-rtr0.neo.rr.com [65.25.128.253]
5 19 ms 19 ms 17 ms son0-1-3.mtgmoh1-rtr0.cinci.rr.com [65.25.128.24
6]
6 19 ms 20 ms 18 ms pop1-cin-P2-0.atdn.net [66.185.133.5]
7 20 ms 19 ms 19 ms bb1-cin-P0-0.atdn.net [66.185.133.0]
8 26 ms 25 ms 25 ms bb1-chi-P3-0.atdn.net [66.185.153.50]
9 27 ms 25 ms 28 ms pop1-chi-P0-0.atdn.net [66.185.141.85]
10 27 ms 25 ms 26 ms GlobalCrossing.atdn.net [66.185.151.222]
11 26 ms 26 ms 28 ms pos8-0-2488M.cr2.CHI1.gblx.net [67.17.67.93]
12 84 ms 83 ms 84 ms so2-0-0-2488M.cr2.MIA1.gblx.net [67.17.93.141]
13 84 ms 83 ms 84 ms pos3-0-0-622M.ar1.MIA1.gblx.net [67.17.67.134]
14 78 ms 78 ms 79 ms Atlantic-Net.gig1-0-0.409.ar1.MIA1.gblx.net [64.
214.106.54]
15 * * * Request timed out.
16 * * *
Very bad! 
These servers are near Orlando, FL. Too many hops.
What about 152.163.159.236 ?
205.188.157.236
129.137.254.4
12 hops before timing out. How many hops is considered OK? I take it that too many hops will drastically slow down my speed here right?
Not really. The DNS responses are cached by XP. Only the first request to resolve a host name requires dns access. I think up to 30ms latency is ok. The overall speed/performance will not be affected.
[QUOTE=Interlink]
If the problem is just your 2 domains, you can define the host names / IP using the local file “hosts”.
[/QUOTE]
Its the customer I am worried about more than I.
Here are a few big ISP nameservers:
4.2.2.4
4.2.2.5
198.6.1.1
198.6.1.2
198.6.1.122
198.6.1.144
Several of those are located in different places, and by two different companies, I might recommend one of the 4. series and one of the 198. series for you two nameservers, it should balance out some.
Also to clear local DNS cache reboot, or in Win2000 go to Start, Run, type in cmd, hit enter. Then at the prompt type in: ipconfig /flushdns
[QUOTE=Stephen]
Here are a few big ISP nameservers:
4.2.2.4
4.2.2.5
198.6.1.1
198.6.1.2
198.6.1.122
198.6.1.144
Several of those are located in different places, and by two different companies, I might recommend one of the 4. series and one of the 198. series for you two nameservers, it should balance out some.
Also to clear local DNS cache reboot, or in Win2000 go to Start, Run, type in cmd, hit enter. Then at the prompt type in: ipconfig /flushdns
[/QUOTE]
One of my sites was dead to me again this morning so I dropped a couple of these numbers in and it became available again.
I wonder how many people have this problem…
Jim - I believe most people will see your site fine for this reason. First time visitors are not usually affected. Only those that have accessed your site recently - i.e. before the dns changes were made. Unless they are using a nameserver that had already cached the old IP of course. Believe me, best not to worry about it. There is little you can do, and it will sort itself out. At least you now know why its happening and how you can (and instruct others how to) get around the problem.
Thanks guys for the tutorial and the nameserver addresses.