Package: network-manager Version: 0.6.5-5 Severity: wishlist Hi,
I'd try to provide a patch, but my C-fu is very, very weak... ISC DHCP 3.1 provides support for the domain-search option. This is the correct way for a DHCP server to provide a domain search list. Wedging multiple domains into the domain-name option is a horrible hack. It seems, however, that that is what NetworkManager expects, and so how it generates an /etc/resolv.conf. This behaviour should be changed in light of dhclient 3.1, and should do something like this: if the domain-search option is present in the data received via DHCP, use it in favour of the domain-name option for setting the search directive in /etc/resolv.conf if the domain-name option is present in the data received via DHCP, use it to set the domain directive in /etc/resolv.conf if only the domain-name option is present in the data received via DHCP (and domain-search is not), for backwards compatibility, set the search directive in /etc/resolv.conf It appears, from my testing, that NetworkManager interacts with resolvconf, so the above only applies when resolvconf is not installed. I've already filed #460609 to have resolvconf update its behaviour. This bug is important for consistent treatment of /etc/resolv.conf when DHCP and the domain-search option is in use. regards Andrew -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
