RE: Caching nameserver -- BIND(?) caching/forwarding server

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Robert Hanson <roberth@xxxxxxxxxxxx> wrote:
> what does your resolv.conf file look like?
> what does your named.conf file look like?

>From what I saw in this thread, the original poster is (was?)
interested in caching for local Windows systems.  That's why
"nscd" came up but was quickly dismissed.

> maybe the thread name should be changed if you are using
> bind or bind caching nameserver

That's why I append the subject to nscd, but now I've
responded and changed it again here.  We started to go off on
"nscd," but then we came back to the BIND or another DNS
caching/fowarding server**.

-- Bryan

**[OT]NOTE:  My primary reason for doing this is that it
makes it easier to find discussions in the archives, while
still reserving the "sort by subject" in the mail readers
too.  It's the same logic that was used prior for UseNet per
the (now lost?) O'Reilly discussion guidelines.  It not only
helps raise my ratings in Google searches, as well as
popularity in people who click on them, but I get thanks from
people who see my subject appendings mid-thread out of dozens
or even hundreds of items (saving them a lot of effort).

Thread ID in SMTP/NNTP always maintains threading proper
(which is why I switched to Yahoo for webmail recently, away
from not only my old provider who didn't, but GMail which has
stated it will never).



-- 
Bryan J. Smith                | Sent from Yahoo Mail
mailto:b.j.smith@xxxxxxxx     |  (please excuse any
http://thebs413.blogspot.com/ |   missing headers)

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux