Since NetworkManager (NM) is default in F10, I want to use NM to manage my eth0, which has a static IP. Since the system is configured with a static IP, there is no DHCP server to assign the system DNS servers. NM overwrites /etc/resolv.conf with generated text. For the "System eth0" connection (i.e. it reads ifcfg-eth0), it attempts to find DOMAIN/DNS1/DNS2/DNS3 entries in ifcfg-eth0. However, system-config-network (s-c-n) doesn't allow editing those interface-specific fields, rather s-c-n's DNS UI writes /etc/sysconfig/networking/profiles/default/resolv.conf, which is completely ignored by NM. As such, I have to go manually edit the ifcfg-* files to make DNS work correctly. What's worse is that something (I think s-c-n?) hard-links /etc/resolv.conf to /etc/sysconfig/networking/profiles/default/resolv.conf, so NM ends up trashing the s-c-n resolv.conf file every time it rewrites /etc/resolv.conf, which I think is every time it brings the interface up. Finally, I note that NM reads DOMAIN from ifcfg-eth0 and translates this to a "search" in resolv.conf, whereas s-c-n writes a "SEARCH" field. I don't know if this aspect of the bug is s-c-n's fault, or NM's fault.
I have the same problem, just upgraded to F10 and NM doesn't let me configure/use static IP, and screws up any working configuration made previously by hand or by s-c-n. This is really a showstopper because now I can't use NM (which I need in order to manage other non-eth0 interfaces). I hope this gets fixed soon...
Bug 475134 describes the resolv.conf trashing aspects of this bug.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.