Bug 446635

Summary: NetworkManager generates somewhat bogus resolv.conf file
Product: [Fedora] Fedora Reporter: Tom Horsley <horsley1953>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 9CC: dcbw, emertens, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: svn3675 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-03 18:21:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
resolv.conf none

Description Tom Horsley 2008-05-15 14:11:11 UTC 
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:
Comment 1 Jesus M. Rodriguez 2008-05-24 01:15:26 UTC 
Created attachment 306557 [details]
resolv.conf

not sure if this is caused by suspending the laptop or not. But seems to be
duplicates.
Comment 2 Eric Mertens 2008-05-24 04:25:02 UTC 
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.
Comment 3 Dan Williams 2008-07-02 23:17:42 UTC 
Does updating to NetworkManager-0.7.0-0.10.svn3675 help the situation?
Comment 4 Eric Mertens 2008-07-03 17:11:56 UTC 
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.
Comment 5 Dan Williams 2008-07-03 18:21:28 UTC 
Ok, thanks for the update!