getting multiple domain-name dns request to work with microsoft windows xp dhcp clients

Glenn Satchell glenn.satchell at
Fri May 28 01:42:35 UTC 2010

Hi Jelle

That's an invalid config that just happens to work for the Linux client 
and was a common workaround before there was a revision to the RFC to 
add a feature for setting the search list. The correct definition for 
option domain-name is a single domain. In this case the MS client is 
behaving correctly.

I am assuming you wish to set the search path for dns queries. The way 
to do this is to use

      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 "", "",


On 05/28/10 05:31, Jelle de Jong wrote:
> Hello everybody,
> I have configured a nice dynamic dns with dhcpd system with bind9 and
> dhcp3-server on debian gnu/linux, and it seemed to be working very well,
> until I attached a Microsoft windows xp dhcp clients and the dns queries
> where not the same as those of the linux clients.
> option domain-name "";
> I know Microsoft DNS can work, because if I manually set the DNS servers
> it works, but manually setting every client is not workable solution for
> me.
> When debugging the bind9 dns request I can what goes wrong in the request:
> 27-May-2010 00:25:45.159 queries: info: client
> query:\ IN A +
> It seems the domain-name set by windows is received as one server with
> spaces in it names instead of receiving two domain-names the client
> should be using.
> I tried some stuff I found at:
> I can't get it to work. Can somebody help me out?
> Thanks in advance,
> With kind regards,
> Jelle de Jong

More information about the dhcp-users mailing list