Description of problem: resolv.conf does not pick up my search line from /etc/dhclient.conf. I end up with no search or domain line. So I end up manually editing it. Not good for usability
Reassigning to NetworkManager maintainer
I know at one time NetworkManager was supposed to notify a running bind process what the new DNS servers were. In that case, the DNS server was supposed to be localhost. If that's what you're seeing, then it's working. Right now I'm seeing that /etc/resolv.conf has the normal entries even though I'm running bind. I wish I could get it to work the other way (with bind on localhost).
Taking ownership.
Is this bug still occuring ? Is it NetworkManager-vpnc specific or is it a general NM issue ? Can you attach your dhclient.conf file, and also verify that it is syntactially correct ? (see /var/log/messages). I'm not even sure you can supersede the search entries... If I don't hear from submitter, will close in a week as WORKSFORME.
Seems to work with Standard Network Manager plugged into wire and on the rh-wireless Definitly broken on NetworkManager-vpnc rpm -q NetworkManager-vpnc NetworkManager-vpnc-0.7.0-0.cvs20060929.2.fc6 With vpnc cat /etc/resolv.conf # generated by NetworkManager, do not edit! nameserver 172.16.52.28 nameserver 10.11.255.27 With just Wireless cat /etc/resolv.conf # generated by NetworkManager, do not edit! search redhat.com redhat.com lab.boston.redhat.com nameserver 66.187.224.210 nameserver 66.187.233.210
Reassigning to vpnc, I don't see how this issue could be caused by n-m-vpnc unfortunately...
The vpnc doesn't pick the search lines from dhclient.conf because it doesn't use dhcp at all. The vpnc's own interface init script (which is probably not in use when vpnc is called from NetworkManager-vpnc) preserves search lines from the original /etc/resolv.conf. So either WONTFIX or back to NetworkManager-vpnc.
*** This bug has been marked as a duplicate of 182011 ***