See hidden discussions | Win great prizes | Get free support
I use lightsquid with my Squid proxy cache, so I checked all the youtube-related hosts that have been accessed over the last month or so of usage, and then through trial-and-error worked out the maximum hosts for each type (r1 to r24 for example). I dumped all the hosts underneath each other in a text file called 'hosts', and then created a simple shell script to do the rest:Fragtion: how did you (or did someone else) compile that list of 400+ entries? I hope you didn't use nslookup for all those numbers to verify whether they exist...
While the "lscache" hosts resolved fine to local, the hosts with "nonxt" didn't. I noticed that there were exactly the same number of nonxt equivalents for the lscache ones, so I just gooi'd the local IP's for them too.#!/bin/sh
rm -rf ips
while read IP ; do
echo $IP `nslookup $IP 18.104.22.168 | grep Add | grep -v '#' | cut -f 2 -d ' '` >> ips
done < hosts
Rough day then Di? I think you'll find Pada was joking. I also think that the help he dishes out getting people sorted using local servers for as much as possible should count in his favour...
* Overriding method: hosts file * ISP account name: TI DoBroadband 1 * URL: [url]https://www.facebook.com/[/url] * Ping results: Time Outs for 22.214.171.124 / 202/ 203 * DNS Server IP address: DNS 1 126.96.36.199 DNS 2 188.8.131.52
Servers often block ICMP (ping) packets. So if you can't ping the server, it doesn't imply that the server is definitely offline!Plus, if you can't ping a website how can you connect to use it? It's MAGIC, I tell you.
C:\Users\Tinuva>tracert mail.google.com Tracing route to googlemail.l.google.com [184.108.40.206] over a maximum of 30 hops: 1 7 ms <1 ms <1 ms router.heaven.za.net [10.0.0.1] 2 12 ms 7 ms 8 ms dsl-185-83-1.dynamic.wa.co.za [220.127.116.11] 3 21 ms 9 ms 8 ms vl105.cr.gw.cpt.za.wa.co.za [18.104.22.168] 4 18 ms 9 ms 8 ms vl40.er.gw.cpt.za.wa.co.za [22.214.171.124] 5 12 ms 36 ms 9 ms 126.96.36.199 6 9 ms 9 ms 9 ms 188.8.131.52 7 9 ms 8 ms 10 ms 184.108.40.206 8 9 ms 8 ms 8 ms cpt01s01-in-f83.1e100.net [220.127.116.11] Trace complete.