From: "Dan Williams" <dcbw@xxxxxxxxxx> > It does work with any static IP address you have configured with > system-config-network. It will apply the IP & DNS configuration you've > selected using system-config-network Profiles on startup. NM blows away > your /etc/resolv.conf because it uses a local caching nameserver to deal > with horrible glibc resolver dropouts when network switches occur. > That's not likely to change, what may change would be the ability to add > custom entries to the caching nameserver's config. That's fine, but the current behaviour is rather brutal: you start it and everything stops working. That can't be good. At the very least can you back-up resolv.conf, and maybe restore it when you shut NM down? I guess that can happen even in the init.d script. Ideally, NM should migrate the content of resolv.conf to bind, so that starting/stopping NM becomes seemless. Also a more explanatory message in the overriden resolv.conf would be appreciated. -- Dimi Paun <dimi@xxxxxxxxxxx> Lattica, Inc. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-devel-list
