Red Hat Bugzilla – Bug 10297
resolv.conf
Last modified: 2008-05-01 11:37:55 EDT
resolv.conf entries lost across boot. I reported this problem earlier today and it appeared to be a problem with ifup-post. After correcting ifup-post with no change in the behavior, I installed the updates for the init scripts off your support page. Still no change. Next, I reinstalled Linux replacing the custom install with a standard work station install. Still no change, the resolv.conf is zapped when Linux is rebooted. I have recursivly greped all directories looking for text strings associated with "resolv" and with the entries that are showing up in my resolv.conf file. Nothing found other than ifup-post. I can only assume that some executable driven at startup is responsible for the problem. The end result of this is that the resolv.conf file must be manually reconstructed after reboot of Linux before any host names can be resolved. Could it be somehow related to the DHCP client? You can call me at 509-893-7404 if you have questions about my configuration.
*** Bug 10293 has been marked as a duplicate of this bug. ***
pump is editing the resolv.conf file - reassigned to pump.
You can turn off pump's mucking with /etc/resolv.conf by creating an /etc/pump.conf that looks like this: --------- device eth0 { nodns } --------- "man pump" documents the pump.conf file format.