Index: [Article Count Order] [Thread]

Date:  Fri, 5 May 2006 09:02:37 -0700
From:  "Adam Crews" <adam.crews (at mark) gmail.com>
Subject:  [coba-e:05060] Re: DNS cacheing
To:  coba-e (at mark) bluequartz.org
Message-Id:  <1486c6440605050902xe35d177k7cead2f32b28594f (at mark) mail.gmail.com>
In-Reply-To:  <957919163.20060505172322 (at mark) gmx.net>
References:  <027601c66fa7$e35fb640$3701a8c0 (at mark) lapxp>	 <957919163.20060505172322 (at mark) gmx.net>
X-Mail-Count: 05060

It is also worthy to note that if you are doing performance tuning,
that nscd will always be faster than running a local named. 
Communicatoin to nscd is done through a much faster IPC socket than
communication to a local caching named.  This probably doesnt matter
unless you are doing a large number of lookups.

-Adam

On 5/5/06, Chris Hemsing <C.Hemsing (at mark) gmx.net> wrote:
> 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
>
>
>


--
-----------------------------------------------------------------
Shroom.net Donation Based Web Hosting
http://www.shroom.net/
-----------------------------------------------------------------