Dan Williams wrote: > On Sat, 2008-02-23 at 19:36 -0800, Howard Chu wrote: >> I run a caching named on my laptop, so I've configured my dhclient to >> write any received DNS server addresses into an >> /etc/named/forwarders.conf file instead of /etc/resolv.conf. However, >> NetworkManager still overwrites my resolv.conf with the remote DNS server >> addresses, even though I've changed my /etc/sysconfig/network options and >> told it not to update resolv.conf any more. (I think I already restarted >> NetworkManager too, so it ought to have read the new config.) > > NetworkManager takes over /etc/resolv.conf while it's running, and > there's an interface to send forwarders to a D-Bus service run by named > that will act as a caching nameserver. If you're running F8 though, > that may have been removed from your named packages already, as it's > somewhat in flux upstream. > >> It seems to me that updating resolv.conf is always the wrong thing to do >> anyway; my computer's FQDN is what it is, no matter what network I >> connect to. Why should my resolv.conf's domain and search list change >> just because I've moved to a different physical location? > > NM may get DNS information from multiple sources, including VPN, > mulitple devices, etc. If you're running in a caching nameserver > situation with a D-Bus enabled caching nameserver that can talk to NM, > you'll only ever see "127.0.0.1" in /etc/resolv.conf. > > Dan Please see my solution: http://nbecker.dyndns.org:8080/misc/local_caching_ns.pdf
_______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
