Package: dhcpcd-base Version: 1:10.0.5-2 Severity: normal Hello and thanks for maintaining this package in Debian!
I am giving it a try (inside a virtual machine), as a drop-in replacement for isc-dhcp-client (with the ifupdown package). 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... Why cannot I have the two search domains on Debian? What's wrong? What did I fail to understand? Shouldn't this work out of the box? Please let me know, thanks for your time. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (800, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-4-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dhcpcd-base depends on: ii adduser 3.137 ii libc6 2.37-12 ii libssl3 3.0.11-1 ii libudev1 254.5-1 dhcpcd-base recommends no packages. Versions of packages dhcpcd-base suggests: pn resolvconf | openresolv | systemd-resolved <none> -- no debconf information
