Sorry, this is the email address I should have opened this bug with.
The bug appears identical to #461056 which was closed with upload of:
dhcp3-client_3.1.0-2_i386.deb
Inspection suggests the patch is no longer in the script.
Changelog notes:
* debian/dhclient-script.{linux,kfreebsd}: stop stripping out literal \032
from $new_domain_search. It only gets in there if the domain-search is
incorrectly specified as a single string of multiple space-separated
domains.
Okay, so the correct syntax for the domain-search option is allegedly;
domain-search "1.example.com","2.example.com";
This works!
This suggests there is a mistake in the dhcp-options manual page, which
describes the syntax as:
"The domain-list data type specifies a list of domain names, a space
between each name and the entire string enclosed in double quotes. These
types of data are used for the domain-search option for example, and encodes
an RFC1035 compressed DNS label list on the wire."
and
"
option domain-search domain-list;
The domain-search option specifies a ’search list’ of Domain Names to be
used by the client to locate not-fully-qualified domain names. The
difference between this option and historic use of the domain-name option for
the same ends is that this option is encoded in RFC1035 compressed labels
on the wire. For example:
option domain-search "example.com", "sales.example.com",
"eng.example.com";
"
Only one of those can be correct, and I was starting to think it was I who was
confused.
I suspect at this point the wise thing to do is either to cope with both
cases, or detect the wrong case and flag it during installation, since it
once did work this way, and was documented to work this way, whether or not
that was the intention.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
