resolv.conf on a nameserver

[Barry Margolin]

In article <7t2ja8$pi4$1 at ultron>,
Hugh Davies <hdavies at kzin_nospam.rnb_nospam.com> wrote:
>Is there any standard as to which nameserver the resolv.conf on a
>nameserver should point to? I usually make them the same as the clients
>of that nameserver, in other words, pointing to itself and the other
>nameservers.

That's pretty reasonable -- if that resolv.conf is good for clients, it
should be good enough for the server itself.  However, in the case of the
machines that are listed 2nd or 3rd on the client machines you may want to
put themselves first in their own resolv.conf files, to reduce latency; on
the other hand, the machine that's first on everyone else's list is likely
to have the fullest cache, so using it may be better (you have the extra
latency of communicating with the server, but you're less likely to have to
go out to the Internet).

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.