dhclient fails to update resolv.conf if DHCP is served by dnsmasq on linux.
This bug is odd and very specific. affects at least OpenBSD 5.9 - 6.0 amd64.
Running OpenBSD on core2duo laptop and vm gives me the same behavior.
If dhclient.conf specifies domain-name, domain-name-servers then all is well.
Default behaviour with no dhclient.conf, such as bsd.rd for fresh install, then
gateway and nameserver must be manually filled in despite being given by
DHCP. Other OSes (mac, linux, windows) on same DHCP service are fine.
/var/db/dhclient.leases shows fully populated information as expected, but
does not populate /etc/resolv.conf by default. As the lease clearly has the
information, and default behavior should be to fill in DNS information, I am
blaming dhclient. I have found no other DHCP server which causes this,
and running dnsmasq on OpenBSD does not induce this problem.
dhclient running in foreground throws no errors during this situation.
I hope this is helpful,
ED.
