Hi again Julian,
> The forwarding statement only changes HOW it goes
> about getting names resolved, it doesn't stop it from caching the results.
> Given the setup I was talking about in the first place was four machines on a
> LAN, one of which was a Linbox running bind, there's no point in running a DNS
> server in the first place if all I'm going to do is concentrate all DNS request
> to the Linbox then pass them up to my ISP's DNS server, is there? I might as
> well point each of my LAN workstations at my ISP's DNS server and be done with
> it. They'd all go my ISP's server individually for their answers.
Well, the first quote contradicts the second. The difference is the caching
done on your local DNS server (which is only forwarding request for which it
can't find the answer in it's cache iiuc). The first lookup to fe
www.redhat.com is forwarded to the forward DNS, but the second is taken from
the cache. Not a lot less traffic in this specific setup, but it *does* reduce
traffic.
> Lastly, the issue of the IP stack resolver on your DNS server itself.
> Actually, the DNS server entries in resolv.conf aren't necessary if the DNS box
> is set to use itself for DNS, which is typical.
You mean you don't need to enter "127.0.0.1" in resolv.conf? I would assume
you need to point the IP stack to the (locally running) DNS server to use it
to resolve names...
Bye,
Leonard.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
