On Thu, 23 Nov 2023 09:01:34 +0100 "Francesco Poli (wintermute)" <invernom...@paranoici.org> wrote: > Package: dhcpcd-base > Version: 1:10.0.5-2 > Severity: normal > > It seems to work pretty well, just like isc-dhcp-client, but > I noticed an issue in a network where the DHCP server sends > two domains as "search domains" (let's call them MYDOMAIN > and OTHERDOMAIN). > > When I use dhcpcd-base as a DHCP client, I get the following > resolv.conf file: > > $ cat /etc/resolv.conf > # Generated by dhcpcd from enp0s3.dhcp > # /etc/resolv.conf.head can replace this line > domain MYDOMAIN > nameserver 192.168.0.1 > # /etc/resolv.conf.tail can replace this line > > This lacks the two search domains I was expecting. > To be honest, the isc-dhcp-client Debian package > behaves similarly (somehow failing to write OTHERDOMAIN as > second search domain). > > But Rocky Linux clients (on the same network, with the ISC > DHCP client and ifup/ifdown mechanism) correctly set the > resolv.conf with the two search domains: > > $ cat /etc/resolv.conf > ; generated by /usr/sbin/dhclient-script > search MYDOMAIN. OTHERDOMAIN. > nameserver 192.168.0.1 > > Even Windows clients (on the same network) correctly obtain > the two search domains...
You might wanna check whether Rocky Linux has patched their DHCP clients or altered their default dhcpcd.conf to make this succeed. If that's the case, please point me to the relevant changes. > Why cannot I have the two search domains on Debian? The dhcpcd client shipped by Debian is, except for recent patches towards fixing the build on Hurd (missing includes, etc.), whatever upstream ships. If that fails to set more than one search domain, I would suspect an upstream issue. https://github.com/NetworkConfiguration/dhcpcd/issues Martin-Éric
