On Fri, Sep 12, 2014 at 07:56:10AM -0400, Minfei Huang wrote:
[..]
The network will get the DNS from the /etc/resolv.conf. The config
resolv.conf generates by the dhcp server, also we can modify it
manually. But the configuration which we add manually to the resolv.conf
will be lost when the network restart.
So in order to solve this problem, we can add the option of PEERDNS=no
to the ifcfg-{*}, the resolv.conf file will not be changed again by the
dhcp server.
The dracut will use own default configuration (in dracut directory) to
configure the network, whatever the custom modify the configuration in
/etc/dhclient.conf.
I send a patch to the dracut community. The patch can only do one thing
that it will append the valid content from /etc/dhclient.conf to
${initdir}/etc/dhclient.conf.
So what does dhclient.conf do?
We(Dave and me) think that the configuratin need to be valid in the
second kernel, if the custom set the own configuration to the
dhclient.conf.
So we should ignore the option of PEERDNS, even if set the option
PEERDNS=no in ifcfg-*.
And the kdump will have no change for this BUG.
Sorry, I still did not get that why should we ignore PEERDNS if
specified in ifcfg*.
Thanks
Vivek