From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (X11; U; Linux 2.4.18-0.13 i686)

Description of problem:
Configuring an ethernet device using redhat-config-network and selecting 'dhcp'
puts
a line 'PEERDNS=no' into the corresponding
/etc/sysconfig/network-scripts/ifcfg-eth0
file. This is especially bad, since it stops pump (or dhcpcd) from generating a
new
/etc/resolv.conf file based on the information received from the DHCP server.

Version-Release number of selected component (if applicable):
redhat-config-network-0.9.21-1


How reproducible:
Always

Steps to Reproduce:
1.Start redhat-config-network
2.Configure ethernet device using dhcp
3.Save changes
	

Actual Results:  The generated file contains named line, while it shouldn't.

Expected Results:  No such line should be generated, at least not until the user
is able to choose himself, if /etc/resolv.conf should be generated or not, ie.
if
PEERDNS=no|yes should be emitted.

Additional info:

This is bad for mostly laptop users who are connecting to different DHCP
servers.
While the first boot after an installation will most likely succeed, any further
attempt
using a *different* DHCP server will fail, because it's unlikely that the
nameserver,
whose address had been emitted into /etc/resolv.conf during the first boot, is
still
accessible.