> ...or even better, considering you're running on Linux, use your own
> computer as a caching nameserver. Most distributions come with a
> caching-only nameserver already configured, so all you have to do is
> enable named at boot up (update-rc.d or chkconfig or whatever) and add
> `nameserver 127.0.0.1' to /etc/resolv.conf.
I won't recomend this for most dialup users. A caching nameserver for only a
single user typically eats up more bw than using the isp's nameserver. Also
many of the bigger sites have a very short expiry time for their www
subdomain, so that can take up bw too! One solution for this is to configure
bind to forward all requests to your isp. That way you will use less bw than
if you set up a nameserver to do recursive queries. This works faster too.
If you are sharing your net connection, then you should definitely use a
caching nameserver at your end. In that case you do end up with some bw
saving and much better response times than using isp's nameserver. Even in
this case, I have seen that a forwarder typically does a better job. If you
use spectranet, then disregard this advice and set up your own nameserver.
Or ask it to forward the queries to one of vsnl's nameservers. Spectranet
seems to have broken nameservers where sometimes it returns "invalid host
name" responses when it can't resolve a domain name!
Ambar
================================================
To unsubscribe, send email to [EMAIL PROTECTED] with unsubscribe in subject header.
Check archives at http://www.mail-archive.com/ilugd%40wpaa.org
