Before I submit as a bug, has anyone else encountered -- doing a fresh, clean install of CentOS-3 results in a resolv.conf with only my secondary nameserver listed and the search domain.
The install works fine, the eth0 and eth1 (onboard e100's) are detected, all the right info entered, etc -- typical by the book textmode (not GUI) install that I'd normally do with RH9/RHEL3. Static IP eth0, 2 nameservers, eth1 unused left at defaults.
Anyone else confirm? Unfortunately the machine is already in production, so wiping and retrying to confirm isn't an option for me. Shoulda thought of that sooner...
-te
On Mon, 12 Apr 2004, Troy Engel wrote:
Before I submit as a bug, has anyone else encountered -- doing a fresh, clean install of CentOS-3 results in a resolv.conf with only my secondary nameserver listed and the search domain.
neat bug -- I have not seen it -- but I use dhcp everywhere, so I never look at the /etc/resolv.conf after an install, and it gets wiped by the dhcp-client every lease renewal; The over-rides of dhclient-script and dhclient.conf do not seem to work according to the man pages in CentOS, but in tracing through the RH scripts, some of the man page options appear to have been not supported.
I would bugzilla it locally, and then check upstream at the RH bugzilla for like reports; I will look for it next time I install; I assume you are setting static IP and resolver information?
-- Russ Herrold
R P Herrold wrote:
install; I assume you are setting static IP and resolver information?
Correct -- I use/used 100% static information.
-te
-
R P Herrold -
Troy Engel