On Tue, 05 Jan 2010 14:30:02 +0000 Patrick O'Callaghan wrote: > That seems to be working for the moment, but there's an element of magic > in it that makes me nervous. The default named.conf file is set up as a > simple cacheing nameserver for local queries, but where does named do > its recursive lookups if not from the DHCP service? If you want to add the name servers specified by DHCP to lookups, then you don't want your resolv.conf file to be unmodified, instead you want NM to modify it "correctly", like by leaving 127.0.0.1 as one nameserver and adding additional nameservers. <sarcasm> How to get NM to do this is no doubt described fully in the extensive NetworkManager documentation. </sarcasm> With bind configured as a cacheing server, there is usually a "forwarders" section in named.conf that points to the DNS servers it should look at. These aren't affected by NM in any way I know of (though it might be nifty if there was some way for NM to add and subtract forwarders dynamically). Don't know if that is possible or not. I suppose it could do something drastic like modify the named.conf file and restart bind. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
