Ubuntu
dhcp3 package

  1. Bug #8634
  2. Comment #5

Comment 5 for bug 8634

Revision history for this message
In , Michael Graham (oobermick-btinternet) wrote : dhcp3-client: dhclient-script only sets resolv.conf when both new_domain_name and new_domain_name_servers exist

Why hasn't this bug been fixed yet? (as of dhcp3_3.0+3.0.1rc11)

The original poster has given a perfectly good fix, although I prefer:

make_resolv_conf() {
   if [ "x$new_domain_name_servers" != x ] || ["x$new_domain_name" != x
] ; then
     rm -f /etc/resolv.conf
     if [ "x$new_domain_name" != x ]; then
       echo search $new_domain_name >/etc/resolv.conf
     fi
     if [ "x$new_domain_name_servers" != x ]; then
       for nameserver in $new_domain_name_servers; do
         echo nameserver $nameserver >>/etc/resolv.conf
       done
     fi
     chmod 644 /etc/resolv.conf
   fi
}

Since it makes new_domain_name_servers and new_domain_name independent.

Anyway, back to the point. Is there a reason why this bug has not been
fixed?