On Tue, 2010-01-05 at 05:17 +0100, Tom H wrote: > >> How does one convince NM not to interfere with resolv.conf? > > > Don't know for sure how to make interfaces managed by NM > > stop doing it, but for my non-NM system I still have to > > prevent resolv.conf from being scrogged by setting > > PEERDNS=no > > in my /etc/sysconfig/network-scripts/ifcfg-eth0 file. > > resolv.conf is overwritten by dhclient, whether the interface is is > NM-managed or not, so your "PEERDNS=no" solution will work for the OP. >
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? poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
