On Fri, Sep 26, 2008 at 03:29, Howard Chu <[EMAIL PROTECTED]> wrote: > The point is that users need a level of control over how name resolution is > done. Once you resort to adding/removing entries from resolv.conf you've > completely removed the possibility of retaining local control over name > resolution. If you leave /etc/resolv.conf pointed at your local caching name > server, you retain full control. You can make local policy decisions about > how to handle any particular name lookup, instead of just blindly walking > down a list of 3 server addresses in a flat file for all lookups.
See, there you go again. Injecting a perceived feature request that no one in this thread has requested. You really must come back to ground level and understand that NO ONE is asking you or NM for fine-grained name resolution control. Nope, no one. The only feature requested was for NM to provide a checkbox style boolean option to enable/disable resolv.conf updating (a'la DNSUpdate in Cisco VPNs) in NM Global options, individual connection settings, and (possibly) as an option per connection type (i.e. wired/wireless). NOTHING MORE. No need to try and push people to use dnsmasq, no need to espouse your great knowledge of all things, no need for you to educate anyone. In fact, a simple "Yes it can be done" or "No, that's impossible to implement" would have sufficed. -Jim P. _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
