Hi Robbie - Well, as you might infer from my previous post, I always save it
as HOSTS. FWIW, I tend to use my HOSTS file a little differently from most
folk, since I do my blocking with a combination of lists that are
consolidated by a program called Confetch and then input to a local DNS
client, Treewalk, here:
http://treewalkdns.com which handles the blocking
as part of its DNS lookup functionality. I therefore use my HOSTS file
almost exclusively to store the URL-to-IP translations of my Favorites, mail
and news server addys, and any links which I may want to override for some
reason that are on the blocking lists (since the HOSTS file is accessed
first before Treewalk does its thing, this lets me go ahead and access the
IP even though it's on the combined Treewalk filter.conf blocking list.)
Here's a little more info on HOSTS files from a 'canned' post about using
them for blocking that may be use:
First, you should understand that the original purpose of the HOSTS file
(BTW, it should always be named this way - all caps, no extension) was to
provide a local (therefore fast) translation from URLs to IP addresses for
frequently visited sites (typically your Favorites). It can still be used
this way (I do so, for example - there are utilities available such as CIP,
http://dl.winsite.com/bin/downl?500000007704 which will convert your
Favorites to IP's which you can then saveas and then copy into your HOSTS
file), but has also come to be used to block ad/malware servers by
redirecting them to your local machine instead of their servers using this
same mechanism. See here for some good info about this use:
http://www.mvps.org/winhelp2002/hosts.htm
This site also has downloads for some utility programs which you will find
useful if you decide to use a HOSTS file such as RenHosts.bat,
http://www.mvps.org/winhelp2002/RenHosts.bat, and lockhosts.bat and
unlockhosts.bat,
http://www.mvps.org/winhelp2002/lockhost.bat, and
http://www.mvps.org/winhelp2002/unlockhost.bat. The lock and unlock files
can be used to protect the HOSTS file in between UPDATES so that it doesn't
get hijacked by malware, while the rename hosts program will allow you to
easily enable or disable the HOSTS file (while keeping the correct naming
convention). An even better approach IMO which I use is HostMan, here:
http://www.abelhadigital.com/ which offers some other useful tools as well.
As to size/performance - with any relatively modern computer the delay added
by the HOSTS lookup overhead should be negligible for even moderately large
HOSTS files (typically 250KB to 500KB) used for ad/malware blocking. If you
use it also for DNS-to-IP caching as I referred to above, the time saved
over going out to the net for DNS lookups will offset this many times. If
fact you may notice some speedup in "normal" address browsing.