Thanks for your great explanation (and everyone else's, for that matter). By using bindconf, I think I've achieved exactly what you suggest. Please see my accompanying post.
j. ================== At 06:24 PM 1/5/02 +0100, you wrote: > Hi Dave, Julian, > > Although most has already been said I can't keep myself from jumping on > this >wagon ;). > > > > I thought (don't ask me where I got this idea) that bind (ie.named) > looked in > > > /etc/hosts first before going to an upstream DNS server. > > > > This is usually true because of the default ordering in /etc/host.conf > > As Chuck explained, this is *not* true. It's the protocol stack or if > you'ld >like to say the kernel that either looks in /etc/host.conf or does a DNS >query >depending on the order in /etc/host.conf when looking up an IP address. > bind uses the config files in /var/named to lookup an IP address for a name >(for the domains it is authoritative for, ie your local domain. It will query >antoher DNS server for the lookup of other IP's.) > If you want to set up a name server for a small domain install the caching- >nameserver.noarch.rpm, add an entry for the local domain zone file in >/etc/named.conf and create the zone file for the local domain in /var/named. > Hope this clears things up. If not, reread Chuck's post, he's the only one >who got it all right afaict. > > Bye, > > Leonard. > > > > >_______________________________________________ >Redhat-list mailing list >[EMAIL PROTECTED] >https://listman.redhat.com/mailman/listinfo/redhat-list ---------------------------------------------------------------- Just because I'm paranoid doesn't mean they aren't after me ... Julian Opificius. ICQ 3268206. ---------------------------------------------------------------- _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
