On Wed, Jul 05, 2006 at 11:20:27PM -0600, joey wrote:
You're still getting a connection to the old server. The new server is 208.99.202.194
Right. I changed the network TTL (the time before a cached IP address expires) from 1 day to 1 hour, so further changes will propagate faster. Depending on what network connection you're using, you might be able to force a cache reload (rebooting your system often works). During my testing earlier, I had it pushing 50Mbp/s. It's been averaging about 8Mbps all day. -- Greg
On Thu, Jul 06, 2006 at 02:40:28PM +1000, rnmscott@netspace.net.au wrote:
PING www.worldebookfair.com (72.235.235.66) 56(84) bytes of data 64 bytes from 72.235.235.66: icmp_seq=1 ttl=110 time=3769 ms 64 bytes from 72.235.235.66: icmp_seq=2 ttl=110 time=3566 ms 64 bytes from 72.235.235.66: icmp_seq=3 ttl=110 time=3628 ms 64 bytes from 72.235.235.66: icmp_seq=4 ttl=110 time=3427 ms 64 bytes from 72.235.235.66: icmp_seq=5 ttl=110 time=3501 ms
Quoting joey <joey@joeysmith.com>:
Can you check which IP address your machine resolves www.worldebookfair.com to? I'm getting 2Mb/s from 208.99.202.194 (the readingroo.ms server). Perhaps your DNS simply hasn't updated, or maybe there's congestion between you and readingroo.ms, but I'd like to know before I try adding some of the rate limiting stuff Greg has asked me to look into.
_______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/listinfo.cgi/gutvol-d