M Harris wrote: > I suppose the way to handle this is to make the first server a caching > nameserver forwarding to the second server and then outside. The second > server then forwards only outside. Changes are made to the second server > *only* (or it caches from outside) and the primary server gets its changes by > caching the second. If the primary is down the secondary gets it. If the > secondary is down the primary forwards to its secondary forwarder (outside). > I'm gonna have to play with this some more.... just for fun... :) >
I missed what you need this for, but if the idea is to provide local DNS for a LAN, while also being able to resolve outside names, you may want to look at the "dnsmasq" package. It's designed to do specifically that, and it's easier to set up than a full-blown nameserver. Of course, if your goal is to learn bind, you should go ahead and work on setting up named.conf to do what you want. :) -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
