Bug 124634 - system-config-network insists on PEERDNS=no
Summary: system-config-network insists on PEERDNS=no
Keywords:
Status: CLOSED DUPLICATE of bug 122846
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-network
Version: 2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-28 01:58 UTC by Michal Jaegermann
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:03:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michal Jaegermann 2004-05-28 01:58:36 UTC
Description of problem:

When configuring an interface for DHCP neat seems to hell-bent
on sticking PEERDNS=no into an interface configuration.  This
means that DNS information will be invalid on another network
with a DHCP server.  At least I could not find another way
but to take an editor and edit in ifcfg-eth0, making sure that
hardlinks are not broken, PEERDNS=yes and after that _do not
touch_ eth0 configuration under any circumstances.

If may not mean very much as the whole interface is hideously
counterintuitive, and inviting to make all kind of mistakes, if
one has anything but the most trivial configuration (an interface
on a single network) to handle.

Component: system-config-network
Version: 1.3.16

Comment 1 Harald Hoyer 2004-06-04 13:10:42 UTC

*** This bug has been marked as a duplicate of 122846 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:03:51 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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