Red Hat Bugzilla – Bug 124634
system-config-network insists on PEERDNS=no
Last modified: 2007-11-30 17:10:43 EST
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.
*** This bug has been marked as a duplicate of 122846 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.