Bug 443592 - empty resolv.conf file using static IP address setup
Summary: empty resolv.conf file using static IP address setup
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: rawhide
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-22 13:09 UTC by Davide Moretti
Modified: 2008-04-28 12:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-28 04:43:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Davide Moretti 2008-04-22 13:09:11 UTC
Description of problem:
COnfiguring eth0 to use a static IP address and setting manual DNS entries in
system-config-network, when using systemwide NetworkManager, results in an empty
/etc/resolv.conf file


Version-Release number of selected component (if applicable):
NetworkManager-0.7.0-0.9.2.svn3566.fc9.i386


How reproducible:
always

Steps to Reproduce:
1. setup eth0 to use a static IP address and enter manual DNS entries
2. cat /etc/resolv.conf (to confirm entered DNS)
3. service NetworkManager restart
4. cat /etc/resolv.conf (empty file)

Actual results:

cat /etc/resolv.conf

# Configured by NetworkManager (do not edit)



Expected results:

cat /etc/resolv.conf

nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx


Additional info:

Adding a eth0  local configuration using the gnome applet works correctly, but
then eth0 would only work when logged into GNOME, and not in runlevel 3 for example.

Comment 1 Dan Williams 2008-04-22 14:15:41 UTC
Try putting DNS1=xxxxxx and DNS2=xxxxxx into your ifcfg-eth0 file (or whatever
the device name you're using is).

Comment 2 Davide Moretti 2008-04-22 18:50:30 UTC
(In reply to comment #1)
> Try putting DNS1=xxxxxx and DNS2=xxxxxx into your ifcfg-eth0 file (or whatever
> the device name you're using is).

This works, but puts only DNS1 value in /etc/resolv.conf, DNS2 is ignored.

So it seems at least that system-config-network needs to be updated to be able
to edit DNS1 and DNS2 in the config filess....

Comment 3 Dan Williams 2008-04-28 04:43:37 UTC
Latest Koji builds fix this issue; please try:

http://koji.fedoraproject.org/koji/buildinfo?buildID=47429

Thanks!

Comment 4 Davide Moretti 2008-04-28 12:26:16 UTC
It works!


Note You need to log in before you can comment on or make changes to this bug.