Description of problem: Here's a sample file generated by NetworkManager: # generated by NetworkManager, do not edit! domain ccur.xen search ccur.xen nameserver 129.134.30.167 Note that both domain and search are specified. This is sorta harmless, but it would really be better to leave off domain and only use search since search is more general and the directives actually conflict with only the last one being used. Version-Release number of selected component (if applicable): NetworkManager-0.7.0-0.9.3.svn3623.fc9.x86_64 How reproducible: Every boot. Steps to Reproduce: 1. boot system, observe /etc/resolv.conf Actual results: conflicting directives Expected results: only a search directive Additional info:
Created attachment 306557 [details] resolv.conf not sure if this is caused by suspending the laptop or not. But seems to be duplicates.
I've had the same experience as seen in the attached file where network manager seems to accumulate every dns server it has ever seen and even has duplicate entries in resolv.conf which often results in the wrong DNS server being selected.
Does updating to NetworkManager-0.7.0-0.10.svn3675 help the situation?
Actually, I have NetworkManager-0.7.0-0.9.4.svn3675.fc9.x86_64 at the moment and the problem seems to be gone now. I'm not experiencing this bug any more.
Ok, thanks for the update!