Question : DNS suffix search via DHCP

My company just merged with another company and we're having some challenges getting DNS suffix search order to work when set by DHCP.

My company (company1.com) and the other company (company2.local) now share a network but our DNS servers don't seem to be resolving any non FQDN name to their addresses. They are configured in our forward lookup zone.

Sooo, we added the DHCP option 135 to our DHCP server with company2.local as the single suffixe in the search.

I'm able to ping FQDN with no trouble but non qualified domain lookups still do not work.

Ping server1.company2.local returns an addy but ping server1 returns "ping request could not find host server1..."

server1 does not have an A record in company1.com.

Any help would be greatly appreciated.


EDIT:

I verified that the suffix search does work if I use Group Policy. Because of my situation, I can't set this option using GP as I'm not the sysadmin for the users of the secondary domain (yet).

Answer : DNS suffix search via DHCP

It still does not work with DHCP Client. Even with the latest SP2 on XP and updates, the client never requests for this option. Options are normally assigned to a client when a request is generated from it. For e.g. WPAD Option 252...The request for the same is generated when you open IE but somehow Clients never request Suffix Order (Search List) from DHCP. I have been involved with a lot of Microsoft Research Group related to DHCP with noone ever coming back with a satisfied answer.


This is what the article has to say...

http://support.microsoft.com/default.aspx?scid=kb;en-us;275553

"""Dynamic Host Configuration Protocol (DHCP). You cannot configure DHCP to send out a domain
suffix search list. This is currently not supported by the Microsoft DHCP server"""

Also, read this..Interesting article....but no longer works with the existing OS.
http://support.microsoft.com/kb/312468/