Hello Arthur,
there are 3 different situations:
1) In case you have named running anyway and you have access to and want to use someones
DNS servers, that are large (high probability for cache hits) and
quick (if they are small or lame, better don't use them!):
in this situation your resolv.conf should look like you said: it
should include the 127.0.0.1 PLUS you should define those two
nameserver as forwarding nameservers in your dns setup (e.g. through
the gui).
What happens is that named will forward your queries and cache the
answers. The lines
Nameserver ISP_DNS_1
Nameserver ISP_DNS_2
will usually not be reached. named does cacheing for you!!!
However these two lines may be very important for situations where named is not running
(may have died or more importantly at early stages of booting).
2) In case you have named running but no other or lame or only small (usually
no cache hits) forwarding servers to contact:
Then let named do everything. Only 127.0.0.1 in resolv.conf and no
forwarding servers. Again named does cacheing.
3) In case you don't have named running: No 127.0.0.1 in
resolv.conf and do consider starting nscd (a pure cache daemon) as it
had been recommended in Adam Crew's mail ([coba-e:05019] Re: The ongoing
QPOPPER Debate)
Chris
Thursday, May 4, 2006, 8:23:41 PM, you wrote:
>> > there should be a named running anyway!!!!!!!!!!!!
>> > Of course named is cacheing!!!!
>> > But - of course - you need to ask your own named.
>> > So resolv.conf should direct to
>> > 127.0.0.1
>> > No further use in a cache daemon!
AS> Do you actually say that my resolv.conf should include as follows?:
AS> Search server_domain.tld
AS> Nameserver 127.0.0.1
AS> Nameserver ISP_DNS_1
AS> Nameserver ISP_DNS_2
AS> Best,
AS> --
AS> Arthur Sherman
AS> +972-52-4878851
AS> CPTeam