Bas Zoetekouw wrote: > > Attached is a patch that should fix this. It adds support for the > domain-search option of dhcp, and uses the logic you suggested to > determine what search domains to put in resolv.conf. > > I have tested the patch only at my local configurationw, which is > n-m + dhcp3-client 3.1.0-2 (no resolvconf) on my laptop, and a pre-3.1 > dhcp3-server on my server (current etch version), and for that config, > it seems to work fine. Testing for other configuration, particular with > a new, post-3.1, dhcpd is probably needed, though. > > Please feel free to send the patch upstream, if you think it's stable > enough. >
Hi Bas, first of all, thanks for the patch. I tested it locally (dhcp server from my wlan router) and my resolv.conf now looks like: domain foo.xx search foo.xx nameserver 192.168.2.1 Is it intended behaviour that now both search and domain are set? Unfortunately I don't have access to a dhcpd 3.1 server, so I can't really test if the new domain-search feature works as intended. Bas, you said that you tested it with dhcpd 3.1 (which according to andrew has domain-search support), so why do you think that we also have to test with post-3.1 dhcpd? Cheers, Michael P.S: I updated the patch to apply against head of the current upstream 0.6 branch and intend to send it for review to the upstream mailing list -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
