Bug 110250 - no refresh of resolv.conf via dhcp
no refresh of resolv.conf via dhcp
Product: Red Hat Linux
Classification: Retired
Component: dhcpcd (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-11-17 10:41 EST by Need Real Name
Modified: 2007-04-18 12:59 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-07-16 09:43:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:566 normal SHIPPED_LIVE Updated dhcp and dhclient packages 2005-05-26 00:00:00 EDT

  None (edit)
Description Need Real Name 2003-11-17 10:41:21 EST
Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot PC on network A obtaining IP address via dhcp having DNS info
for A
2. Shutdown PC
3. Boot PC on network B obtaining IP address via dhcp having DNS info
for B
Actual results:

The initial resolv.conf file stays in /etc instead of being replaced
by a new one. The IP number is that of the network attached to. The
second boot is extremely slow on all network related components
(sendmail, httpd, gnome, etc.)
Expected results:
A new resolv.conf file based on the info provided by the dhcp server
of the attached network.

Additional info:
I found the following (recent) post via Google describing more or less
the same problem: 


Comment 1 Daniel Walsh 2003-12-29 08:22:28 EST
Looks like dhclient will not rewrite the /etc/resolv.conf on a renewal
of an IP Address.

  if [ x$reason != xRENEW ] && [ "${PEERDNS}" != "no" ]; then 

If you do a service network restart, does the resolv.conf get updated?

Comment 2 Need Real Name 2004-01-02 08:25:43 EST
I tried a network restart (# /etc/init.d network restart) without
success. Removed the resolv.conf and did another restart: no
resolv.conf gets created.

Client system is out of the box RH9. DHCP server at home is out of the
box RH8; at work DHCP is Win2K SP3.

Comment 3 Jason Vas Dias 2004-07-16 09:43:35 EDT
This doesn't appear to be a problem with latest version of scripts in
dhcp-3.0.1rc14-1 .
It sounds like one of the dhcp servers in this case was not supplying
DNS server addresses ; if the dhcp server does not supply DNS server
addresses, no resolv.conf gets written - this is correct.
The lines Dan mentions:
 if [ x$reason != xRENEW ] && [ "${PEERDNS}" != "no" ]; then 
are now:
    if [ "${PEERDNS}" != "no" ]; then 
This should fix this issue (if it was caused by the PC renewing
and not by the dhcp server not supplying DNS server addresses).
So, I'm closing this bug as resolved.
Comment 4 John Flanagan 2004-12-21 14:42:09 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.