Bug 398351 - No way to set custom DNS with DHCP connection
Summary: No way to set custom DNS with DHCP connection
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 8
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-25 13:40 UTC by Rohan Dhruva
Modified: 2007-12-04 05:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-12-03 21:13:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Rohan Dhruva 2007-11-25 13:40:35 UTC
Description of problem:
Hi, I'm using NetworkManager on gnome with fedora 8, installed using the live
cd. On my DHCP connection, I need to set custom DNS to access any site .. The
default 192.168.1.1 doesn't cut it. On other distros like ubuntu/debian I can
edit /etc/dhcp3/dhclient.conf or something equivalent. However on fedora there
is no way to set the custom dns. I tried editing the settings in
system-config-network, however NM always overrides it and mangles my
/etc/resolv.conf. I also tried making /etc/resolv.conf read-only after suitably
editing it, however it was replaced the next time NM connected. Please include a
suitable way to manage custom DNSes in fedora.

Version-Release number of selected component (if applicable):
0.7.0-0.5.svn3030.fc8

How reproducible:
Always

Steps to Reproduce:
1. Edit /etc/resolv.conf
2. Restart DHCP connection
  
Actual results:
/etc/resolv.conf is modified to include only one entry - 192.168.1.1

Expected results:
There should be some way to set custom DNS

Additional info:
How are DHCP connections managed on fedora ? Is there something equivalent to
/etc/dhcp3/dhclient.conf like on ubuntu ?

Comment 1 Dan Williams 2007-12-03 15:27:04 UTC
yes, you probably want /etc/dhclient.conf.  Options set there are the same
options you'd set in /etc/dhcp3/dhclient.conf.  It's just in a different place.

Comment 2 Rohan Dhruva 2007-12-03 19:04:46 UTC
You don't think I wouldn't have tried out everything before filing a bug, do you
? :)
That file doesn't exist on my system. I had the same problem in fedora 7.

Comment 3 Dan Williams 2007-12-03 21:13:41 UTC
You can simply create the file and fill it out like you need.  There's usually
no need for that file unless you wish to override the default DHCP behavior,
therefore it doesn't need to exist until you need it.

Comment 4 Rohan Dhruva 2007-12-04 05:13:51 UTC
Ah, that worked wonderfully. Thank you, Dan.  :)
I think this should be mentioned in the documentation somewhere..


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