<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Dan Williams wrote: <blockquote cite="mid1210081105.21415.3.camel@localhost.localdomain" type="cite"> <pre wrap="">Since the DNS info is not necessarily global to the entire machine, but can be per-device, you probably want to define DNS servers and search domains directly in the ifcfg files as is done for PPP connections already. Updated versions of NetworkManager will place a note in /etc/resolv.conf pointing this out if it can't find any DNS servers. The problem is that resolv.conf is transient. It's created from a _composite_ of the DNS information from multiple connections. For example, if I'm on a VPN, I need the nameservers for both my normal (eth0) connection and the VPN connection, but the VPN may only resolve names for the private network, not the internet as a whole. But I certainly don't want the VPN nameserver listed in resolv.conf when I'm not connected to the VPN. That sort of thing. Dan </pre> </blockquote> Well, I would think in this scenario of supporting per-device name resolution that /etc/resolv.conf would act as a 'global' db and the /etc/sysconfig/network-scripts/ifcfg* files would be the per-device db. But NM should not just erase your /etc/resolv.conf. That's just wrong. You fill in all the info it its gui and then save and then sometime later at some random time it just decides its going to erase /etc/resolv.conf. Very bad. Besides, I have many tools/scripts that work against /etc/resolv.conf and of course I would have to rewrite these if I wanted them to support per-device dns. But I shouldn't have to if I only want a global dns nameserver db in /etc/resolv.conf. Regards, Gerry </body> </html>