> From: Julian Opificius <[EMAIL PROTECTED]> <snip>
> >I'm still not convinced that using the forwarders isn't the > >best/correct solution. > > For you or me it certainly may be the _best_ solution - because it reduces > the work done by our local DNS server :-) Correct vs incorrect is not a > useful assessment in my eyes, as it would certainly work. > > > >From man named.conf (BTW, does anybody else on a RedHat 7.2 system get > >strange lines when typing "man named.conf" - it outputs a bunch of > >lines like "mdoc warning: Empty input line #2064" before getting to > >the man page). > > I'd worry about that if I were you ;-) Strange - I found a couple other man pages that do that, but not all of them. Guess I'll check the man page RPM and maybe force its reinstall and see if it still happens and then post to the enigma list if it still does. > >----------------------------------------------------------------- > > > > Forwarding > > > >The forwarding facility can be used to create a large site-wide cache > >on a few servers, reducing traffic over links to external nameservers. > >It can also be used to allow queries by servers that do not have > >direct access to the Internet, but wish to look up exterior names > >anyway. Forwarding occurs only on those queries for which the server > >is not authoritative and does not have the answer in its cache. > > > >----------------------------------------------------------------- > > > >Again this (specifically the last line) seems to indicate this is what > >to do. If the answer can be found in my machine's DNS cache, it is > >used, otherwise it uses my ISPs nameservers to do all the work (and > >then presumably caches the result). > > Any DNS server does that. That's what DNS serving is :-) Even a DNS server > that talks to a forwarder does caching. The only difference is that if (and > only if, by the way, unless you have the entry "forward only") the local > DNS server is successful in getting an IP resolved by the upstream > (forwarding) DNS server, then it doesn't have to do the Sherlock Holmes > work itself. Which is to say that if the upstream server doesn't get the > job done "in time", then the local DNS server will go out and do the work > itself, forwarding statement or no. > > It's perfectly OK to use your ISP's server as a forwarding server, I'm not > saying it's not. If you have a busy or a slow machine it's not a bad idea. > All I am saying is that doing so in a single-DNS server network is not what > the forwarding feature was intended for. That is no reason not to use it > though ! > > Julian. I agree with what you're saying. I guess I meant "best/correct" in the sense that if it's found in the cache it's used (earlier I thought you were saying the forwarding bypassed the local cache) and if not it has my ISPs DNS servers do all the work (which is what I want). Dave _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
