On Fri, May 16, 2008 at 11:33:14PM +0200, Mario 'BitKoenig' Holbe wrote: > Hi, > > I stumbled across this bug because I tried to implement domain-search > for me and did also get the "Invalid domain list." error. > > On Fri, Feb 01, 2008 at 05:23:46PM -0700, Neil Mayhew wrote: > > 0130 07 77 30 77 79 63 6c 69 66 66 65 2e 63 61 20 63 .w0wycliffe.ca c > > 0140 61 6c 2e 77 79 63 6c 69 66 66 65 2e 63 61 20 64 al.wycliffe.ca d > > 0150 68 63 70 2e 63 61 6c 2e 77 79 63 6c 69 66 66 65 hcp.cal.wycliffe > > 0160 2e 63 61 2c 04 ac 10 01 08 ff .ca,...... > > Neil: Looks like this data is not correctly encoded according to RFC > 3397. Perhaps this is why this error occurs. What DHCP server are you > running? > > Andrew: For me, this is reproducible as follows: > My DHCP client runs on Debian unstable, i.e. dhcp3-client 3.1.1-1, which > supports the domain-search option. > My DHCP server runs on Debian stable, i.e. dhcp3-server 3.0.4-13, which > does not support the domain-search option. Thus, I tried to define it as > option domain-search code 119 = text; > in my dhcpd.conf and subsequently added a > option domain-search "foo.com bar.org"; > This way I'm getting the "Invalid domain list." error on the DHCP > client. And, of course, since dhclient3 cannot decode the domain list, > it does also not appear in dhclient-script.debug. > > RFC 3397 defines the search list to be encoded as defined in RFC 1035. > Newer dhcp3-server define a new domain-list data-type for that. I'm not > sure if this data-type can be emulated on older versions. >
It can't, which is why you're having the problem. You can define your own option on both the non-3.1.x server, and the 3.1.x client, and then it should work, but it won't be the correct format for other clients (e.g. MacOS X). That said, someone[1] was adamant that they were doing exactly that, and it did work for MacOS X. Perhaps its DHCP client is more tolerant. [1] https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/98618 regards Andrew
signature.asc
Description: Digital signature
